[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] big brother replacement
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] big brother replacement
- From: Sloan <joe (at) tmsusa.com>
- Date: Mon, 05 Nov 2007 11:31:46 -0800
- References: <FB13116A8C464943B4A5436A616C95F80BCB0816 (at) rocexu01> <472BB636.3080400 (at) tmsusa.com> <961092e10711021817g146ca321jac5f53721f05737a (at) mail.gmail.com> <472BDCD9.6080706 (at) tmsusa.com> <961092e10711021946q71b59cd2sd7e2c864e27f021 (at) mail.gmail.com> <472F5F17.1090900 (at) tmsusa.com> <997a524e0711051043p5345e51eocfc4e2734ae11cec (at) mail.gmail.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070801 SUSE/2.0.0.6-22 Thunderbird/2.0.0.6 Mnenhy/0.7.5.0
Ralph Mitchell wrote:
> In your original email you said:
>
> "only one of the bb servers does reporting, as determined by the
> failover state"
>
> Does that mean only one of the two sends out notifications?? If so,
> why not just have two identical Hobbit servers, with all the clients
> sending reports to both, and disable the [bbpage] section in
> server/etc/hobbitlaunch.cfg on the backup system. Then your failover
> solution only has to detect "death of twin" and rewrite the
> hobbitlaunch.cfg with DISABLED removed from that section. I guess
> Hobbit might need to be reloaded or restarted for the change to take
> effect.
>
> I haven't tried this - we don't use the paging system - I'm just
> wondering if something as simple as that might work.
>
Yes, that approach has merit, it could work.
However I still need to give Henrik's quick solution from last week some
testing - I'm currently building a hobbit infrastructure so I can see
how his failover script behaves under pressure.
Joe