[Pacemaker] A demand to the process trouble.(OpenAIS/Corosync and Pacemaker)
renayama19661014 at ybb.ne.jp
renayama19661014 at ybb.ne.jp
Fri Jul 17 01:34:04 UTC 2009
Hi,
We began shift investigation to the combination of Pacemaker and corosync/openais now.
We put Pacemaker and openais(whitetank) together and confirmed movement at the time of the process
trouble.
(This is the function that a reboot emergency occurred by a combination with Heartbeat.)
I let a process of Pacemaker break down. (kill -9 pid)
The following behavior was seen then.
* When crmd reboots on ACT node(Not DC), the monitor of the lrmd resource stops.
And the monitor of the stonnith resource stops.
* When stonithd reboots on ACT node(Not DC), the monitor of the stonnith resource stops.
* When crmd reboots on STB node(DC), the monitor of the stonnith resource stops.
* When pengine reboots on STB node(DC), the monitor of the stonnith resource stops.
* And more....
We feel a problem for the stop of the monitor after the process reboot.
When we combined openais/corosync, we hope a function such as the urgent reboot of Heartbeat to be
included.
Best Regards,
Hideo Yamauchi.
More information about the Pacemaker
mailing list