Hi, The slave should know the master is unable to complete monitor operations. If any monitor operations fail, it should initiate fencing. But because the OS is so rammed, it doesn't respond to anything. But it appears as if the slave doesn't initiate any health checks at all against the master, so never knows its failed, this is crazy.
Regards, James Smith -----Original Message----- From: linux-ha-boun...@lists.linux-ha.org [mailto:linux-ha-boun...@lists.linux-ha.org] On Behalf Of Florian Haas Sent: 11 July 2011 08:39 To: General Linux-HA mailing list Cc: Warnke, Eric E Subject: Re: [Linux-HA] Antw: Re: Forkbomb not initiating failover On 2011-07-08 15:23, Warnke, Eric E wrote: > > If the fork bomb is preventing the system from spawning a health > check, it would seem like the most intelligent course of action would > be to presume that it failed and act accordingly. Here we go again. Since the original poster did not address the following question of mine, maybe you are inclined to: > Now please define how exactly Pacemaker would be handling this > "accordingly." Florian _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
