On Mon, Aug 1, 2022 at 2:33 PM Josef Johansson <josef@xxxxxxxxxxx> wrote: > > > > > -------- Forwarded Message -------- > Subject: rbd-mirror stops replaying journal on primary cluster > Date: Thu, 2 Jun 2022 16:29:33 +0200 (CEST) > From: Josef Johansson <josef@xxxxxxxxxxx> > To: ceph-users@xxxxxxx <ceph-users@xxxxxxx> > > > > Hi, > I'm running ceph octopus 15.2.16 and I'm trying out two way mirroring. > Everything seems to running fine except sometimes when the replay stops > at the primary clusters. > This means that VMs will not start properly until all journal entries > are replayed, but also that the journal grows by time. > I am trying to find out why this occurs, and where to look for more > information. > I am currently using rbd --pool <pool> --image <image> journal status to > see if the clients are in sync or not. > Example output when things went sideways > minimum_set: 0 > active_set: 2 > registered clients: > [id=, commit_position=[positions=[[object_number=0, tag_tid=1, > entry_tid=4592], [object_number=3, tag_tid=1, entry_tid=4591], > [object_number=2, tag_tid=1, entry_tid=4590], [object_number=1, > tag_tid=1, entry_tid=4589]]], state=connected] > [id=bdde9b90-df26-4e3d-84b3-66605dc45608, > commit_position=[positions=[[object_number=5, tag_tid=1, > entry_tid=19913], [object_number=4, tag_tid=1, entry_tid=19912], > [object_number=7, tag_tid=1, entry_tid=19911], [object_number=6, > tag_tid=1, entry_tid=19910]]], state=disconnected] > Right now I'm trying to catch it red handed in the primary osd logs. But > I'm not even sure if that's the process that is replaying the journal.. > Regards > Josef Anyone who can chime in on this? It seems that journal is useless in it's current state since the local client stops replaying commits after a while. Regards Josef _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |