Thanks - hopefully I'll hear back from devs then as I can't seem to find
anything online about others encountering the same warning, but I surely can't
be the only one!
Would it be the rbd subsystem I'm looking to increase to debug level 15 or is
there another subsystem for rbd mirroring?
What
Thanks - side tracked with other work so only just got around to testing this.
Unfortunately when enabling rbd-mirror logs on the source cluster I'm not
seeing any events logged at all, however on the remote cluster I can see
constant activity (mostly imageReplayer, mirrorStatusUpdater, etc. log
We have rbd-mirror daemon running on both sites, however replication is only
one way (i.e. the one on the remote site is the only live one, the one on the
primary site is just there for if we ever need to set up two-way, but this is
not currently set up for any replication - so it makes sense th
With RBD Mirroring configured from Site A to Site B, we typically see 2
snapshots on the source side (current and 1 previous) and 1 snapshot on the
destination side (most recent snapshot from source) - this has been the case
for over a year now.
When testing a DR scenario (i.e. demoting the pri
I've had rbd mirror deployed for over a year copying images from Site A to Site
B for DR.
After introducing an additional node into the cluster a few weeks back and
creating OSD's on this node (no mon/mgr) we've started to see snapshots
throwing an error 'librbd::mirror::snapshot::CreatePrimary
Hi,
Following the introduction of an additional node to our Ceph cluster, we've
started to see unlink errors when taking a rbd mirror snapshot.
We've had RBD mirroring configured for over a year now and it's been working
flawlessly, however after we created OSD's on a new node we've receiving t
