memcached losing connections

Eric pytechd at gmail.com
Wed Jan 23 03:43:37 UTC 2008


Brian,

Does that still hold true on FreeBSD 6.2 (and up)? I don't think I've
had any major systemic issues running on localhost on 6.2, but I have
to admit I haven't checked entirely too closely.

On Jan 22, 2008 9:55 PM, Brian Aker <brian at tangent.org> wrote:
> Hi!
>
> I suspect that this is the problem I and Sean looked at while at the
> hackathon. FreeBSD's (and OSX) network stack do not properly flush on
> close() localhost.
>
> Cheers,
>         -Brian
>
>
> On Jan 22, 2008, at 5:53 PM, Kevin Dalley wrote:
>
> > Yes, this is against localhost.
> >
> > When the tests are run against a different machine (though under
> > Linux),
> > the problem goes away.
> >
> >
> > On Tue, 2008-01-22 at 15:43 -0800, Brian Aker wrote:
> >> Hi!
> >>
> >> On Jan 22, 2008, at 9:51 AM, Kevin Dalley wrote:
> >>
> >>> client.  The libmemcached test case "./testapp generate_nonblock"
> >>> reliably shows this problem.  The client is stuck in a poll, waiting
> >>> for
> >>> the ability to write on a socket.
> >>
> >>
> >> Is this against localhost?
> >>
> >> Cheers,
> >>      -Brian
> >>
> >> --
> >> _______________________________________________________
> >> Brian "Krow" Aker, brian at tangent.org
> >> Seattle, Washington
> >> http://krow.net/                     <-- Me
> >> http://tangent.org/                <-- Software
> >> http://exploitseattle.com/    <-- Fun
> >> _______________________________________________________
> >> You can't grep a dead tree.
> >>
>
> --
> _______________________________________________________
> Brian "Krow" Aker, brian at tangent.org
> Seattle, Washington
> http://krow.net/                     <-- Me
> http://tangent.org/                <-- Software
> http://exploitseattle.com/    <-- Fun
> _______________________________________________________
> You can't grep a dead tree.
>
>
>


More information about the memcached mailing list