On 14/06/2013, at 3:52 PM, Xiaomin Zhang zhangxiao...@gmail.com wrote:
Hi, Andrew:
If I cut down the network connection of the running node by:
service network stop,
crm status will show me the node is put into OFFLINE status. The affected
resource can also be failed over to another
Thanks Andrew.
Yes, the fs_ssn service (ocf:FileSystem) is still running when the machine
loses network. I configure it as primitive:
primitive fs_ssn ocf:heartbeat:Filesystem \
op monitor interval=15s \
params device=/dev/drbd0 directory=/drbd fstype=ext3 \
meta target-role=Started
Hi, Andrew:
With the configuration I pasted in this thread, I can see the resource fail
over to the online node when the other node is put into Standby by using
crm node standby command. And when I put the Standby node back again to
Online, the resource keeps running on the original Online node,
On 13/06/2013, at 5:15 PM, Xiaomin Zhang zhangxiao...@gmail.com wrote:
Thanks Andrew.
Yes, the fs_ssn service (ocf:FileSystem) is still running when the machine
loses network. I configure it as primitive:
primitive fs_ssn ocf:heartbeat:Filesystem \
op monitor interval=15s \
Andrew Beekhof andrew@... writes:
Try increasing your stickiness as it is being exceeded by the location
constraints.
For the biggest stick, try 'infinity' which means - never move unless the
node dies.
Thanks, Andrew, I applied infinity resource stickiness. However, the sst
resource is
On 13/06/2013, at 2:43 PM, Xiaomin Zhang zhangxiao...@gmail.com wrote:
Andrew Beekhof andrew@... writes:
Try increasing your stickiness as it is being exceeded by the location
constraints.
For the biggest stick, try 'infinity' which means - never move unless the
node dies.
Thanks,
On 09/06/2013, at 12:19 PM, Xiaomin Zhang zhangxiao...@gmail.com wrote:
Hello, Pacemaker Gurus:
My HA (2 active/slave nodes and 1 standby node) setup contains 1 DRBD
master/slave resource group, and 1 simple lsb resource. I configure some
location constraints to prefer the active node, and I
