On 11/29/2017 04:54 PM, Ken Gaillot wrote:
On Wed, 2017-11-29 at 14:22 +0000, Adam Spiers wrote:
The same questions apply if this troublesome node was actually a
remote node running pacemaker_remoted, rather than the 5th node in
the
cluster.
Remote nodes don't join at the crmd level as cluster nodes do, so they
don't "start up" in the same sense, and start-up fencing doesn't apply
to them. Instead, the cluster initiates the connection when called for
(I don't remember for sure whether it fences the remote node if the
connection fails, but that would make sense).
According to link_rsc2remotenode() and handle_startup_fencing(), similar
"startup-fencing applies to remote nodes too. So if a remote resource
fails to start, the remote node will be fenced. A global setting
statup-fencing=false will change the behavior for remote nodes too.
Regards,
Yan
_______________________________________________
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
