HAST: primary might get stuck when there are connectivity problems with secondary

[Pawel Jakub Dawidek]

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. recv(2)
>  PJD> on secondary doesn't timeout?
> 
> No problems on secondary. When emulating a network outage, after connectivity
> restoring the worker is restarted when new connections comes from primary:
> 
> 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=tank
> Apr 29 14:12:39 hastb hastd: [tank] (secondary) Initial connection from tcp4://172.20.66.201:44508.
> Apr 29 14:12:39 hastb hastd: [tank] (secondary) Worker process exists (pid=1729), stopping it.
> Apr 29 14:12:39 hastb hastd: [tank] (secondary) Worker process (pid=1729) exited gracefully.
> Apr 29 14:12:39 hastb hastd: [tank] (secondary) Incoming connection from tcp4://172.20.66.201:44508 configured.
> 
> 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.

-- 
Pawel Jakub Dawidek                       http://www.wheelsystems.com
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20100429/8eab149c/attachment.pgp