[ClusterLabs] why is node fenced ?

Lentes, Bernd bernd.lentes at helmholtz-muenchen.de
Wed Aug 19 10:22:23 EDT 2020

----- On Aug 18, 2020, at 7:30 PM, kgaillot kgaillot at redhat.com wrote:

>> > I'm not sure, I'd have to see the pe input.
>> You find it here:
>> https://hmgubox2.helmholtz-muenchen.de/index.php/s/WJGtodMZ9k7rN29
> This appears to be a scheduler bug.
> The scheduler considers a migration to be "dangling" if it has a record
> of a failed migrate_to on the source node, but no migrate_from on the
> target node (and no migrate_from or start on the source node, which
> would indicate a later full restart or reverse migration).
> In this case, any migrate_from on the target has since been superseded
> by a failed start and a successful stop, so there is no longer a record
> of it. Therefore the migration is considered dangling, which requires a
> full stop on the source node.
> However in this case we already have a successful stop on the source
> node after the failed migrate_to, and I believe that should be
> sufficient to consider it no longer dangling.

Thanks for your explananation Ken.
For me a Fence i don't understand is the worst that can happen to a HA cluster.

Helmholtz Zentrum München

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

More information about the Users mailing list