Project

General

Profile

Actions
Copy link

Bug #52672

closed

RGW should not recreate ops log socket if it already exists

Added by Cory Snyder over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Cory Snyder
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When RGW daemons start, they recreate the ops log socket if it already exists. This is not ideal because clients of the socket must have special logic to detect when the socket has been recreated in order to continue listening. RGW daemons should attempt to just reuse an existing socket when possible.

Actions
Copy link
 #1

Updated by Cory Snyder over 2 years ago

  • Tracker changed from Fix to Bug
  • Status changed from New to Rejected
  • Regression set to No
  • Severity set to 3 - minor

It turns out that it isn't possible in Linux to reuse an existing Unix socket without first unlinking it. Closing this issue since the suggested fix is not workable.

Actions
Copy link

Also available in: Atom PDF