On 21 Aug 2012, at 17:29, David Lang <[email protected]> wrote: > On Tue, 21 Aug 2012, Jon Heese wrote: >> Feel free to keep discussing alternatives, but I am not at liberty to >> change this system from the current Heartbeat/Pacemaker/CRM\ >> architecture. >> >> Does anyone have any ideas about making my setup do what I'm asking? >> Any comments on my idea of switching to OCF and hacking the resource >> script to never run the "stop" command (except maybe on shutdown or >> some other cases that I haven't thought of yet ;))? > > The simple answer is to just not have heartbeat manage Apache. > > Start Apache from the standard system-wide init scripts (or systemd, > upstart, etc) > > Heartbeat doesn't need to know that Apache exists for this to work. > > What you loose is the ability for heartbeat to notice that Apache is > down and failover from that system, but in my experience that's not a > very valuable capability in the first place (the number of outages > caused by Apache going down is dwarfed by the number of outages caused > by the application not working, when Apache is healthy)
Well, see, that's the thing: These are just reverse-proxy Apache servers... Apache *is* the "application". If the back-end application servers fail in any way, the proxy servers don't (and shouldn't) care. The only things this cluster is concerned with is the shared IP and the apache service itself. We originally built this cluster without the apache resource, but then we had a false positive on our service monitoring app that scared us into thinking that Apache died on the active node yesterday morning. This made us decide to add the apache resource. But now we're in a quandary between here and there... I renew my call for anyone who knows of a way to leave a resource running on all nodes at once. Are there any developers on this list that may know of more esoteric options for the OCF and/or LSB resource types, or do I have to join the developer list for that? Thanks. Jon Heese Systems Administrator Weld County Computer Services ACS Government Systems, Inc., A Xerox Company tel: 970-304-6570 x2552 [email protected] Confidentiality Notice: This electronic transmission and any attached documents or other writings are intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this communication in error, please immediately notify sender by return e-mail and destroy the communication. Any disclosure, copying, distribution or the taking of any action concerning the contents of this communication or any attachments by anyone other than the named recipient is strictly prohibited. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
