The usual reason for blacklisting RBD clients is breaking an exclusive lock because the previous owner seemed to have crashed. Blacklisting the old owner is necessary in case you had a network partition and not a crash. Note that this is entirely normal and no reason to worry. Paul -- Paul Emmerich Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH Freseniusstr. 31h 81247 München www.croit.io Tel: +49 89 1896585 90 On Sat, Aug 3, 2019 at 1:15 PM Kees Meijs <kees@xxxxxxxx> wrote: > > Hi list, > > Yesterday afternoon we experienced a compute node outage in our OpenStack (obviously Ceph backed) cluster. > > We tried to (re)start compute instances again as fast as possible, resulting in some KVM/RBD clients getting blacklisted. The problem was spotted very quickly so we could remove the listing at once while the cluster was coping fine with the boot storm. > > Question: what can we do to prevent the blacklisting? Or, does it make sense to completely disable the mechanism (doesn't feel right) or maybe configure it differently? > > Thanks! > > Regards, > Kees > > -- > https://nefos.nl/contact > > Nefos IT bv > Ambachtsweg 25 (industrienummer 4217) > 5627 BZ Eindhoven > Nederland > > KvK 66494931 > > Aanwezig op maandag, dinsdag, woensdag en vrijdag > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |