[Linux-cluster] Working of a two-node cluster

[emmanuel segura]

you delay parameter in one your fence device, you need to notice the
node with the delay will win the fencing race

The delay used here should usually be at least 5 seconds or more, to
give one node enough time to complete the fencing operation before the
other node begins. This may need to be adjusted based on the actual
amount of time it takes the fence action to complete.

2015-04-24 14:53 GMT+02:00 Jatin Davey <jashokda at cisco.com>:
> Here is my cluster.conf file
>
> ************************
> <?xml version="1.0"?>
> <cluster config_version="4" name="****">
>         <clusternodes>
>                 <clusternode name="node-103" nodeid="1">
>                         <fence>
>                                 <method name="Method01">
>                                         <device name="node-103"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>                 <clusternode name="node-105" nodeid="2">
>                         <fence>
>                                 <method name="Method02">
>                                         <device name="node-105"/>
>                                 </method>
>                         </fence>
>                 </clusternode>
>         </clusternodes>
>         <cman expected_votes="1" two_node="1"/>
>         <fencedevices>
>                 <fencedevice agent="fence_ipmilan" auth="password"
> ipaddr="x.x.x.x" lanplus="on" login="admin" name="node-103" passwd="*****"
> privlvl="ADMINISTRATOR"/>
>                 <fencedevice agent="fence_ipmilan" auth="password"
> ipaddr="x.x.x.x" lanplus="on" login="admin" name="node-105" passwd="******"
> privlvl="ADMINISTRATOR"/>
>         </fencedevices>
>         <fence_daemon post_join_delay="120"/>
>         <rm>
>                 <resources>
>                         <netfs export="/test" force_unmount="1" fstype="nfs"
> host="x.x.x.x" mountpoint="/test/test/test" name="test123"/>
>                         <ip address="x.x.x.x" sleeptime="5"/>
>                         <script file="/xxx/xxx/xxx/xxx/xx.sh" name="xxxx"/>
>                 </resources>
>                 <failoverdomains>
>                         <failoverdomain name="Failover01" nofailback="1"
> ordered="1">
>                                 <failoverdomainnode name="node-103"
> priority="1"/>
>                                 <failoverdomainnode name="node-105"
> priority="2"/>
>                         </failoverdomain>
>                 </failoverdomains>
>                 <service domain="Failover01" name="Service01"
> recovery="relocate">
>                         <ip ref="x.x.x.x"/>
>                         <netfs ref="test123"/>
>                         <script ref="xxxx"/>
>                 </service>
>         </rm>
> </cluster>
>
>
> On 4/24/2015 6:01 PM, emmanuel segura wrote:
>>
>> please share your cluster config, maybe in this way someone can help you.
>>
>> 2015-04-24 14:12 GMT+02:00 Jatin Davey <jashokda at cisco.com>:
>>>
>>> Hi
>>>
>>> I am using a two node cluster using RHEL 6.5. I have a very fundamental
>>> question.
>>>
>>> For the two node cluster to work , Is it mandatory that both the nodes
>>> are
>>> "online" and communicating with each other ?
>>>
>>> What i can see is that if there is communication failure between them
>>> then
>>> either both the nodes are fenced or the cluster gets into a "stopped"
>>> state
>>> (Seen from output of clustat command).
>>>
>>> Apologies if my questions are naive. I am just starting to work with RHEL
>>> cluster add-on.
>>>
>>> Thanks
>>> Jatin
>>>
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>>
>>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster



-- 
esta es mi vida e me la vivo hasta que dios quiera