[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Advice on how to handle HA monitoring
- To: hobbit (at) hswn.dk
- Subject: Advice on how to handle HA monitoring
- From: Charles Jones <jonescr (at) cisco.com>
- Date: Fri, 21 Sep 2007 12:11:42 -0700
- Authentication-results: sj-dkim-4; header.From=jonescr (at) cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
- Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1328; t=1190401981; x=1191265981; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jonescr (at) cisco.com; z=From:=20Charles=20Jones=20<jonescr (at) cisco.com> |Subject:=20Advice=20on=20how=20to=20handle=20HA=20monitoring |Sender:=20; bh=DUOyPjHTZyzvk1M6J2AR7Rv4T/ymy6/qYYB40A2dpD0=; b=LxZEjqdZF61q66a5X+LyIzFVc+mvJpiwOlKmMqG9ZWsU48tjBtp8u+xAXYVkfzCgMYomsVGT QKQIqeLfIxSld26v7OLg7VriBeumb0IG2E6QCmWPVwuTiRDY28QaK5OR;
- User-agent: Thunderbird 2.0.0.5 (X11/20070719)
We have 2 hosts, HostA and HostB. They are part of an HA cluster via HP
ServiceGuard. There is a virtual IP and DNS name of "virtual" that
automatically goes to whichever of HostA and HostB is the primary at the
time.
I am currently monitoring both HostA and HostB via Hobbit. Currently
HostA is the primary, and I am doing various PROC checks. Currently on
HostB, I am not doing process checks.
My problem is, how do I smoothly handle a failover scenario (HostB
becoming the primary)? When a failover occurs, all of the procs on
HostA are stopped (either by the server crashing, or manualy by
ServiceGuard), and the same procs are started up on HostB.
I'm trying to think of ways to monitor both hosts, but only monitor
procs on the one that is primary. So far the best I can come up with is
to run the hobbit clients in local mode, and maybe have the ServiceGuard
scripts swap out the config files and restart the Hobbit clients when
there is a failover. That would probably work, BUT in this case the
Hobbit homdir is also the same (SAN mount) on both machines, so moving
or editing a file on one does the same on the other :(
Simply shutting down the hobbit client on the non-primary is not an
option, as then it would no longer be monitored at all.
Any ideas? :)
-Charles