[Pacemaker] stonith on node-add

[Andrew Beekhof]

On Thu, Jan 31, 2013 at 9:36 AM, Andreas Kurz <andreas at hastexo.com> wrote:
> On 2013-01-30 20:51, Matthew O'Connor wrote:
>> Hi!  I must be doing something stupidly wrong...  every time I add a new
>> node to my live cluster, the first thing the cluster decides to do is
>> STONITH the node, and despite any precautions I take (other than
>> flat-out disabling STONITH during the reconfiguration).  Is this
>> normal?  I'm currently running (sadly) Pacemaker 1.1.5.  It's not a big
>> deal, just inconvenient, though it disturbs me regarding the stability
>> of the other cluster nodes - not that they go down, but I want to know
>> that what I'm doing isn't putting them at risk, either.
>
> this is expected, the default is to fence unseen nodes to "clear" their
> state .... the cluster-property to influence this behavior:
>
> startup-fencing (boolean, [true]): STONITH unseen nodes

Which is also really really really astoundingly incredibly dangerous
to turn on permanently.

>
> Regards,
> Andreas
>
> --
> Need help with Pacemaker?
> http://www.hastexo.com/now
>
>>
>> Thanks!!
>>
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>
>
>
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>