2010/7/27 Andrew Beekhof <and...@beekhof.net>: > On Tue, Jul 27, 2010 at 8:44 AM, Keisuke MORI <keisuke.mori...@gmail.com> > wrote: >> For heartbeat, I personally like "pacemaker on" in ha.cf :) > > One thing thats coming in 1.1.3 is an mcp (master control process) and > associated init script for pacemaker. > This means that Pacemaker is started/stopped independently of the > messaging layer. > > Currently this is only written for corosync[1], but I've been toying > with the idea of extending it to Heartbeat. > In which case, if you're already changing the option, you might want > to make it: legacy on/off > Where "off" would be the equivalent of starting with -M (no resource > management) but wouldn't spawn any daemons. > > Thoughts?
I have a several concerns with that change, 1) Is it possible to recover or cause a fail-over correctly when any of the Pacemaker/Heartbeat process was failed? (In particular, for the failure of the new mcp process of pacemaker and for the current heartbeat's MCP process failure) 2) Would the daemons used with respawn directive such as hbagent(SNMP daemon) or pingd work as compatible? 3) After all, what would be the benefit for end users with the change? I feel like it's only adding some complexity to the operations and the diagnostics by the end users. I guess that I would only use "legacy on" on the heartbeat stack... -- Keisuke MORI _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
