[ClusterLabs] [Question] About movement of pacemaker_remote.

[David Vossel]

----- Original Message -----
> 
> > On 14 Mar 2015, at 10:14 am, David Vossel <dvossel at redhat.com> wrote:
> > 
> > 
> > 
> > ----- Original Message -----
> >> 
> >> Failed actions:
> >>     snmp2_start_0 on sl7-01 'unknown error' (1): call=8, status=Timed Out,
> >>     exit-reason='none', last-rc-change='Thu Mar 12 14:26:26 2015',
> >>     queued=0ms, exec=0ms
> >>     snmp2_start_0 on sl7-01 'unknown error' (1): call=8, status=Timed Out,
> >>     exit-reason='none', last-rc-change='Thu Mar 12 14:26:26 2015',
> >>     queued=0ms, exec=0ms
> >> -----------------------
> > 
> > Pacemaker is attempting to restore connection to the remote node here, are
> > you
> > sure the remote is accessible? The "Timed Out" error means that pacemaker
> > was
> > unable to establish the connection during the timeout period.
> 
> Random question: Are we smart enough not to try and start pacemaker-remote
> resources for node's we've just fenced?

we try and re-connect to remote nodes after fencing. if the fence operation
was 'off' instead of 'reboot', this would make no sense. I'm not entirely 
sure how to handle this. We want the remote-node re-integrated into the cluster,
but i'd like to optimize the case where we know the node will not be coming
back online.

> 
> 
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://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
>