Date: Sat, 4 Jun 2011 16:33:08 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r222688 - head/sbin/hastd Message-ID: <BA66495E-AED3-459F-A5CD-69B91DB359BC@lists.zabbadoz.net> In-Reply-To: <201106041601.p54G1Ut7016697@svn.freebsd.org> References: <201106041601.p54G1Ut7016697@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 4, 2011, at 4:01 PM, Maxim Sobolev wrote: > Author: sobomax > Date: Sat Jun 4 16:01:30 2011 > New Revision: 222688 > URL: http://svn.freebsd.org/changeset/base/222688 > > Log: > Read from the socket using the same max buffer size as we use while > sending. What happens otherwise is that the sender splits all the > traffic into 32k chunks, while the receiver is waiting for the whole > packet. Then for a certain packet sizes, particularly 66607 bytes in > my case, the communication stucks to secondary is expecting to > read one chunk of 66607 bytes, while primary is sending two chunks > of 32768 bytes and third chunk of 1071. Probably due to TCP windowing > and buffering the final chunk gets stuck somewhere, so neither server > not client can make any progress. I don't know about the hast internal protocol but the above reads kind of wrong to me. -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA66495E-AED3-459F-A5CD-69B91DB359BC>