Re: Cluster blacklists MDS, can't start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 6, 2020 at 2:45 PM Patrick Donnelly <pdonnell@xxxxxxxxxx> wrote:

> On Wed, Mar 11, 2020 at 10:41 PM Robert LeBlanc <robert@xxxxxxxxxxxxx>
> wrote:
> >
> > This is the second time this happened in a couple of weeks. The MDS locks
> > up and the stand-by can't take over so the Montiors black list them. I
> try
> > to unblack list them, but they still say this in the logs
> >
> > mds.0.1184394 waiting for osdmap 234947 (which blacklists prior instance)
>
> Do not *ever* unblacklist an MDS. Restart the daemon.
>

These messages showed up after the MDS was restarted right after the boot
messages.

What was actually happening was the MDS was busy reading the journal which
took about an hour to do. I'm not sure why in this situation the journal
got so big, but it was not due to the blacklist, just a coincidence that it
happened to be the same amount of time as the blacklist timeout.

----------------
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux