Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 04 Jul 2010 09:45:36 +0300
From:      Mikolaj Golub <to.my.trociny@gmail.com>
To:        "hiroshi\@soupacific.com" <hiroshi@soupacific.com>
Cc:        freebsd-fs@freebsd.org, Pawel Jakub Dawidek <pjd@FreeBSD.org>
Subject:   Re: HAST and CARP
Message-ID:  <86pqz3iw33.fsf@kopusha.home.net>
In-Reply-To: <4C2F3E14.1080601@soupacific.com> (hiroshi@soupacific.com's message of "Sat, 03 Jul 2010 22:41:40 %2B0900")
References:  <4C139F9C.2090305@soupacific.com> <86iq5oc82y.fsf@kopusha.home.net> <4C14215D.9090304@soupacific.com> <20100613003635.GA60012@icarus.home.lan> <20100613074921.GB1320@garage.freebsd.pl> <4C149A5C.3070401@soupacific.com> <20100613102401.GE1320@garage.freebsd.pl> <86eigavzsg.fsf@kopusha.home.net> <20100614095044.GH1721@garage.freebsd.pl> <868w6hwt2w.fsf@kopusha.home.net> <20100614153746.GN1721@garage.freebsd.pl> <86zkyxvc4v.fsf@kopusha.home.net> <4C2C43D5.1080907@soupacific.com> <86mxubndrp.fsf@kopusha.home.net> <4C2D7615.5070606@soupacific.com> <861vbm1hpr.fsf@zhuzha.ua1> <4C2D9C62.4050105@soupacific.com> <86wrtez14z.fsf@zhuzha.ua1> <4C2DC801.5080108@soupacific.com> <86iq4xx9fy.fsf@kopusha.home.net> <4C2F3E14.1080601@soupacific.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Sat, 03 Jul 2010 22:41:40 +0900 hiroshi@soupacific.com wrote:

 >>
 >> You should have a setup so when the master is rebooted after the reboot it
 >> checks the status of other node and sets its own role accordingly (so there
 >> would not be two masters simultaneously). Software I use in my setup (our home
 >> made application) does this well. sysutils/heartbeat should work fine too. As
 >> for me carp might not do well for this but I am not very experienced with carp
 >> so I can be wrong.
 >>

 h> By CARP, ifconfig carp0 advskew {bigger value than secondary} on
 h> console sets CARP as secondary.

 h> How do you think this idea ?

I think you could make a configuration so when hostB (secondary) switches to
master it changes advskew to the value lower then on hostA. In this way after
hostA reboot it will have higher advskew and will be forced to do as a
secondary. Then after the nodes are synchronized you can switch to the initial
state restoring initial value of advskew on hostB.

-- 
Mikolaj Golub



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86pqz3iw33.fsf>