rbd-mirror: admin socket path names collision
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.
#5 Updated by Nathan Cutler about 2 years ago
@Jason 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.