From owner-freebsd-fs@FreeBSD.ORG Tue Feb 22 20:50:16 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31D161065673 for ; Tue, 22 Feb 2011 20:50:16 +0000 (UTC) (envelope-from prvs=0279125ef=Christian.Vogt@haw-hamburg.de) Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by mx1.freebsd.org (Postfix) with ESMTP id B405C8FC0A for ; Tue, 22 Feb 2011 20:50:15 +0000 (UTC) Received: from dehawshub01.mailcluster.haw-hamburg.de ([141.22.200.36]) by mail3.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 22 Feb 2011 21:40:06 +0100 Received: from dehawscas02.mailcluster.haw-hamburg.de (141.22.200.34) by DEHAWSHUB01.mailcluster.haw-hamburg.de (141.22.200.36) with Microsoft SMTP Server (TLS) id 8.1.358.0; Tue, 22 Feb 2011 21:40:06 +0100 Received: from [172.20.0.20] (141.22.200.51) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Tue, 22 Feb 2011 21:40:06 +0100 MIME-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset="us-ascii" From: Christian Vogt In-Reply-To: <86ei713vny.fsf@kopusha.home.net> Date: Tue, 22 Feb 2011 21:40:05 +0100 Content-Transfer-Encoding: quoted-printable Message-ID: <8B15C618-4560-4ABE-BD8E-94872A33F5F6@haw-hamburg.de> References: <2C4EE30F-7731-4B84-ADC6-75C0266863F0@haw-hamburg.de> <86ei713vny.fsf@kopusha.home.net> To: Mikolaj Golub X-Mailer: Apple Mail (2.1082) Cc: freebsd-fs@FreeBSD.org Subject: Re: hastd Failover with ucarp X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2011 20:50:16 -0000 >=20 > On Mon, 21 Feb 2011 16:55:35 +0100 Christian Vogt wrote: >=20 > CV> Hello!=20 >=20 > CV> Thanks for the great work, I like this straight-forward FreeBSD a = lot > CV> from what I experienced untill now. I used the HAST How-To from > CV> http://wiki.freebsd.org/HAST and it works perfectly if I use = "pkill -USR2 > CV> -f 'ucarp -B'" to initiate the failover. The secondary node = becomes > CV> primary and the carp-interface is switched over to it. >=20 > CV> But if I do a hard shutdown of the primary node it doesn't work, = the > CV> secondary node doesn't get primary. The ucarp-up script on the = secondary > CV> node is executed, but it fails because of the still running = secondary > CV> worker process (Secondary process for resource test is still = running > CV> after 30 seconds). Is the secondary process expected to end > CV> automatically, when the primary process fails? >=20 > I think it should exit but currently it does not. In r207371 timeouts = for > primary incoming and outgoing and secondary outgoing were added but = not for > secondary incoming. After keep alive mechanism was implemented I think = we can > add timeout for secondary incoming too. E.g. like in the attached = patch? >=20 > With the patch the secondary will exit in 20 seconds if it does not = receive > any packets from the primary. >=20 > Or may by it is better to replace RETRY_SLEEP with timeout = configuration > parameter, both for keep alive/reconnection interval in primary and = secondary > incoming timeout? >=20 > --=20 > Mikolaj Golub >=20 > Thanks for your help, this solved the issue! I'm still going to use the = carp+devd variant as proposed by Freddie, but this seems to be a good = failover if carp doesn't work properly. Christian Vogt=