I have seen this behavior on several virtualsed environments. when vm
backup starts, the VM actually freezes for a (short?) Period of time.I
guess it then no more responding to the other cluster nodes thus triggering
unexpected fail over and/or fencing.I have this kind of behavior on VMware
env
Hi all. I was hoping to get some help with my configuration. I'm kinda
stuck at the moment.
I've made some changes to the Raid1 RA to implement a ms style
configuration (you can see a diff here http://pastebin.com/Q2nbF6Rg
against the RA in the github repo)
I've modeled my ms implementation
Hi All,
I ran into a time out issue while failing over from master to the peer
server and I have a 2 node setup with 2 resources. Though it was working all
along, this was the first time this issue is seen for me.
It fail with following error 'error: process_lrm_event: LRM operation
Hi Andrew,
Okay!
I test your patch.
And I inform you of a result.
Many thanks!
Hideo Yamauchi.
- Original Message -
From: Andrew Beekhof and...@beekhof.net
To: renayama19661...@ybb.ne.jp; The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Cc:
Date:
On 9 Oct 2014, at 5:06 pm, Alexandre alxg...@gmail.com wrote:
I have seen this behavior on several virtualsed environments. when vm backup
starts, the VM actually freezes for a (short?) Period of time.I guess it then
no more responding to the other cluster nodes thus triggering unexpected
Hi Andrew,
I applied three corrections that you made and checked movement.
I picked all abort processing with g_source_remove() of services.c just to
make sure.
* I set following abort in four places that carried out g_source_remove
if (g_source_remove(op-opaque-repeat_timer) ==
