Date: Thu, 29 Apr 2010 17:45:23 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Mikolaj Golub <to.my.trociny@gmail.com> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: HAST: primary might get stuck when there are connectivity problems with secondary Message-ID: <20100429154523.GH1697@garage.freebsd.pl> In-Reply-To: <86iq7ajyek.fsf@zhuzha.ua1> References: <86r5m9dvqf.fsf@zhuzha.ua1> <20100423062950.GD1670@garage.freebsd.pl> <86k4rye33e.fsf@zhuzha.ua1> <20100424073031.GD3067@garage.freebsd.pl> <868w8dgk4e.fsf@kopusha.onet> <86tyqzeq84.fsf@kopusha.onet> <20100428214636.GD1677@garage.freebsd.pl> <86mxwmk7my.fsf@zhuzha.ua1> <20100429081200.GB1697@garage.freebsd.pl> <86iq7ajyek.fsf@zhuzha.ua1>
next in thread | previous in thread | raw e-mail | index | archive | help
--dwWFXG4JqVa0wfCP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 29, 2010 at 02:22:59PM +0300, Mikolaj Golub wrote: > On Thu, 29 Apr 2010 10:12:00 +0200 Pawel Jakub Dawidek wrote: > PJD> Good. And I assume you don't observe problems on secondary? Eg. rec= v(2) > PJD> on secondary doesn't timeout? >=20 > No problems on secondary. When emulating a network outage, after connecti= vity > restoring the worker is restarted when new connections comes from primary: >=20 > Apr 29 14:12:39 hastb hastd: Accepting connection to tcp4://0.0.0.0:8457. > Apr 29 14:12:39 hastb hastd: Connection from tcp4://172.20.66.202:8457 to= tcp4://172.20.66.201:44508. > Apr 29 14:12:39 hastb hastd: tcp4://172.20.66.201:44508: resource=3Dtank > Apr 29 14:12:39 hastb hastd: [tank] (secondary) Initial connection from t= cp4://172.20.66.201:44508. > Apr 29 14:12:39 hastb hastd: [tank] (secondary) Worker process exists (pi= d=3D1729), stopping it. > Apr 29 14:12:39 hastb hastd: [tank] (secondary) Worker process (pid=3D172= 9) exited gracefully. > Apr 29 14:12:39 hastb hastd: [tank] (secondary) Incoming connection from = tcp4://172.20.66.201:44508 configured. >=20 > If the FS is idle (there is no I/O) secondary is waiting in receive, does= not > timeout and does not stop workers (as it was with my timeout patch). Thanks for reporting and testing. I committed the patch to HEAD. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --dwWFXG4JqVa0wfCP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvZqZIACgkQForvXbEpPzThlQCeNyMDteysX00LN9CbtkMWdeTL 0uQAn3mem/elULuaQSuU0RZw0ZI4P3As =FCrh -----END PGP SIGNATURE----- --dwWFXG4JqVa0wfCP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100429154523.GH1697>