On Fri, Apr 27, 2012 at 10:17:46AM +0800, Zhimin Wu wrote: > Dear Sir/Madam: > > I have questions about Heartbeat 3.0. Could you please tell me how much > nodes Heartbeat 3.0 can support?
How many do you need? Known limitation is not number of nodes, but size and rate of messages exchanged. > If I run a Multi-Process program in several nodes, > could this program be declined as a service monitored by Heartbeat? Most likely. But are you looking for Heartbeat, specifically, or are you looking for Pacemaker? Even though pacemaker continues to work on the heartbeat cluster communication layer, the preferred communication layer nowadays is corosync. http://www.clusterlabs.org/doc/ (there is also the "clusterlabs menu" navigation in the top left corner) > and the last question is can I decline my function to deal with > the node error and insert into Heartbeat? if so, How to do it ? Maybe you can give a bit more context about what you really want to achieve. I'm not sure if you want to "just" make sure some specific services are up and running, if you want to hook up your own fencing agent, or if you are trying to reinvent the wheel and do your own cluster management. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ 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
