On Tue, Apr 9, 2019 at 10:40 AM Magnus Grönlund <mag...@gronlund.se> wrote: > > Hi, > We have configured one-way replication of pools between a production cluster > and a backup cluster. But unfortunately the rbd-mirror or the backup cluster > is unable to keep up with the production cluster so the replication fails to > reach replaying state.
Hmm, it's odd that they don't at least reach the replaying state. Are they still performing the initial sync? > And the journals on the rbd volumes keep growing... > > Is it enought to simply disable the mirroring of the pool (rbd mirror pool > disable <pool>) and that will remove the lagging reader from the journals and > shrink them, or is there any thing else that has to be done? You can either disable the journaling feature on the image(s) since there is no point to leave it on if you aren't using mirroring, or run "rbd mirror pool disable <pool>" to purge the journals. > Best regards > /Magnus > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Jason _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
