Mailing List Archive: Application level HA using heartbeat.. ??

Hi,

I was trying to understand how Heartbeat actually works. I found out that Heartbeat provides HA at a system level rather than application level, meaning the Virtual IP is moved to backup system only on a system-down-scenario and not when application monitored goes down. I verified this. I had configured httpd in my haresources file and I manually stopped httpd using "service httpd stop". Although this stops httpd service, Heartbeat doesn't recognize this. ..!!
But when I stop heartbeat or bring down my machine, Backup comes up and starts httpd. Is this the correct scenario.. if so, please let me know why I should provide a script in resources.d/ to start, stop and find status of the application. Also, how can I achieve application level HA using heartbeat..!
Thanks in advance.. :)

Regards,
Ravikiran N

_______________________________________________
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

On 08/01/2014 03:47 AM, N, Ravikiran wrote:
> Hi,
>
> ... I had configured httpd in my haresources file and I
> manually stopped httpd using "service httpd stop". Although this stops
> httpd service, Heartbeat doesn't recognize this.

Correct, that is how haresorces mode works. It is well documented -- or
was until linux-ha folks removed the documentation from the web because
"heartbeat's old".

> ... why I should provide a script in resources.d/ to start, stop and
> find status of the application. Also, how can I achieve application
> level HA using heartbeat

If you don't want to roll your own scripts, use new corosync/pacemaker
hotness instead of old and busted heartbeat/haresources.

--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Mailing List Archive

Mailing List Archive

Attached Files: