On Fri, 2008-09-05 at 12:45 +0200, Dejan Muhamedagic wrote: [...]
> > > Of course. Well, something like 15 or 20 seconds should fit the > > > bill. If it goes higher than that then perhaps it should be > > > considered to be an outage. That depends on your > > > setup/users/services. Of course, there's no hard rule on what do > > > on high host load. > > > > There are times when the load is around 40, Today I saw it at 50. Uggh. > Wow! Any money left in the budget for more resources? ;-) It is just a matter of engineering the solution. > > these are the times when a > > timeout of 30s is not enough. > > > > Currently I have very little monitoring. Actually *no* monitoring of > > resources and only a couple of ping nodes. > > But you do monitor the IP address. That's a resource too. Yeah, I know. When "failures" occurred the resources would stop on the one node and migrate to the other. This never improved anything and just caused more outages. So I need to take care of the load first, then start monitoring resources again. Cheers, -- Matt Zagrabelny - [EMAIL PROTECTED] - (218) 726 8844 University of Minnesota Duluth Information Technology Systems & Services PGP key 1024D/84E22DA2 2005-11-07 Fingerprint: 78F9 18B3 EF58 56F5 FC85 C5CA 53E7 887F 84E2 2DA2 He is not a fool who gives up what he cannot keep to gain what he cannot lose. -Jim Elliot
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
