[Pacemaker] Unnecessary shuffling of master/slave resources and maybe a split brain

[Adrian Chapela]

Dominik Klein escribió:
> Adrian Chapela wrote:
>> Dominik Klein escribió:
>>>> What are you saying me ? I should have another communication 
>>>> channel as a COM port... I could test this with a null modem cable.
>>>
>>> You need at least 2 connections between the nodes. It never was 
>>> different.
>>>
>>> It once was true that a null modem oder serial cable as the second 
>>> connection was enough - from my _personal_ experience, having 2 
>>> ethernet connections is better (because faster and able to cope with 
>>> the rather high traffic of v2 (pacemaker)).
>> I tested two options. I think the best option is a second ethernet 
>> card. I have configured this option but I saw that my cluster didn't 
>> do a failover.
>> The two connections are in different networks (One in 192.168.18.X 
>> and other in 172.16.1.0) but I don't know why pingd isn't going down 
>> all of resources.
>>
>> I have this connectivity constraint:
>>        <rsc_location id="mail-connectivity" rsc="Mail-drbd">
>>                <rule id="mail-pingd-prefer-rule" score="-INFINITY" 
>> role="Master">
>>                        <expression id="mail-pingd-prefer" 
>> attribute="pingd" operation="lt" value="1000"/>
>>                </rule>
>>        </rsc_location>
>>
>>
>>
>>        <rsc_location id="samba-connectivity" rsc="Samba-drbd">
>>                <rule id="samba-pingd-exclude-rule" score="-INFINITY" >
>>                        <expression id="samba-pingd-exclude" 
>> attribute="pingd" operation="lt" value="1000"/>
>>                </rule>
>>        </rsc_location>
>>
>> And this colocation:
>> <rsc_colocation id="mail_drbrd_rule" rsc="Mail" with-rsc="Mail-drbd" 
>> with-rsc-role="Master" score="INFINITY"/>
>> <rsc_colocation id="samba_drbrd_rule" rsc="Samba" 
>> with-rsc="Samba-drbd" with-rsc-role="Master" score="INFINITY"/>
>>
>> The node lost connectivity with 192.168.18.0 (I defined all host in 
>> this  network for pingd) and pingd value should be less than 1000.
>
> Should be or is?
It Should be changing value but it isn't changing it.
(To know I am using: watch -n1 "cibadmin -Ql | grep status-.*-pingd" )

Pingd is writing this to log;
pingd[3181]: 2008/11/20_17:17:42 info: ping_read: Retrying...
>
> Could you post your xml including the status section in this situation?
Yes, first I will compile the new version of Pacemaker because pingd was 
broken in other versions and this could be the same.
>
> Regards
> Dominik
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at clusterlabs.org
> http://list.clusterlabs.org/mailman/listinfo/pacemaker
>