[Pacemaker] standby attribute and same resources running at the same time

[Andrew Beekhof]

On 15/03/2013, at 11:29 AM, Leon Fauster <leonfauster at googlemail.com> wrote:

> Am 04.03.2013 um 18:20 schrieb Leon Fauster <leonfauster at googlemail.com>:
>> okay - recap: 
>> 
>> 1st. i have this delay where the two nodes dont see each 
>> other (after rebooting) and the result are resources running on both 
>> nodes while they should only run on one node - this will be corrected 
>> by the cluster it self but this situation should not happen.
>> 
>> 2nd. the standby attribute (and there must be a reason why redhat 
>> added this) will prevent to migrate resources to that node. How 
>> do i delete this attribute?
> 
> 
> well - i am still frustrated :-)

Did you get anywhere since?

> 
> Some testing here shows following behaviour: 
> 
> if i boot my two nodes and start cman only (messaging) the cluster comes up. 
> Testing now: if i do a hard shutdown on node2 - node1 begins to "fence" the 
> node2 because this is a test environment i do a fence_ack_manual and boot the 
> node2 again. after starting cman again node2 joins immediately the cluster. 
> thats all without pacemaker.
> 
> 
> if i do the same with cman+pacemaker running and resources started, the second
> node will not join the cluster after rebooting it. 

anything from cman or fenced to indicate they might still want to fence the rebooted node?
can we see some logs from both nodes?

> 
> so far for today
> 
> --
> LF  
> 
> 
> _______________________________________________
> 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