From owner-freebsd-bugs@FreeBSD.ORG  Thu Aug 28 06:47:06 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3E269D9C
 for <freebsd-bugs@FreeBSD.org>; Thu, 28 Aug 2014 06:47:06 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 25221186F
 for <freebsd-bugs@FreeBSD.org>; Thu, 28 Aug 2014 06:47:06 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7S6l6L5064419
 for <freebsd-bugs@FreeBSD.org>; Thu, 28 Aug 2014 06:47:06 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192889] accept4 socket hangs in CLOSED (memcached)
Date: Thu, 28 Aug 2014 06:47:06 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: arne.claus@trivago.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192889-8-CVY56BDPzc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192889-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192889-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 06:47:06 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192889

--- Comment #5 from Arne Claus <arne.claus@trivago.com> ---
We did another test with FreeBSD9, memcached 1.4.20 and libevent 2.x.
This time the server did not get stuck.

We do see different behavior in both servers though.
On FreeBSD 9 we see the CLOSED and CLOSE_WAIT values staying at one number (0
or an initial, low value) for a long time. On FreeBSD 10 they are constantly
increasing and decreasing.
We poll these values in intervals of 1 second so it looks like FreeBSD 10 holds
the connections in these states a lot longer?

What we also see on both systems (in much higher quantities on FreeBSD 10) is
that connections get stuck in CLOSE_WAIT and move to CLOSED after quite a long
time (about two hours).

Can someone explain this behavior or describe what's the differences between
the two systems in that area?

It might help solving the bug or find a faster reproduction rule.
I assume that there is a race condition - involving the libevent code of
memcached - which is just happening more often on FreeBSD 10 due to the
seemingly slower handling of closed connections.

-- 
You are receiving this mail because:
You are the assignee for the bug.