Bug #19907
closedrbd-mirror: admin socket path names collision
0%
Description
For every pool replayer rbd-mirror initializes separate local and remote ceph contexts. During initialization they use 'admin_socket' configuration parameter for admin socket path name. This usually leads to path name collision and admin socket binding failure (the only way to make them unique is to use '$cctid' meta variable for 'admin_socket' config setting, but then it is impossible for a user to know the path name in advance, which complicates its use).
As a result users can't run commands available via admin sockets, e.g. to dump perf counters statistics for the replayed images, which could be very useful for troubleshooting or developing statistics monitoring tools.
Updated by Mykola Golub almost 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Jason Dillaman almost 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20008: kraken: rbd-mirror: admin socket path names collision added
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20009: jewel: rbd-mirror: admin socket path names collision added
Updated by Nathan Cutler almost 7 years ago
@Jason Borden There is no PoolReplayer::print_status in jewel, so the backport would have to be done manually in src/tools/rbd_mirror/Replayer.cc (looks like). However, the PoolReplayer::print_status in master is completely different from Replayer::print_status in jewel.
Updated by Jason Dillaman almost 7 years ago
@Nathan Weinberg: since this is more of a nice-to-have, I am also fine just dropping the need for a backport to jewel (and kraken is about to be replaced by luminous w/o a single point release).
Updated by Nathan Cutler almost 7 years ago
- Status changed from Pending Backport to Resolved