Return-Path: 
 <dev-return-5504-apmail-cassandra-dev-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-dev-archive@www.apache.org
Delivered-To: apmail-cassandra-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id DE18C9AB1
	for <apmail-cassandra-dev-archive@www.apache.org>;
 Thu, 15 Mar 2012 09:53:27 +0000 (UTC)
Received: (qmail 93387 invoked by uid 500); 15 Mar 2012 09:53:27 -0000
Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org
Received: (qmail 93342 invoked by uid 500); 15 Mar 2012 09:53:26 -0000
Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cassandra.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cassandra.apache.org>
List-Post: <mailto:dev@cassandra.apache.org>
List-Id: <dev.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list dev@cassandra.apache.org
Received: (qmail 93329 invoked by uid 99); 15 Mar 2012 09:53:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 09:53:25 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of schumi.han@gmail.com
 designates 209.85.212.178 as permitted sender)
Received: from [209.85.212.178] (HELO mail-wi0-f178.google.com)
 (209.85.212.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 09:53:19 +0000
Received: by wibhq7 with SMTP id hq7so3010839wib.7
        for <dev@cassandra.apache.org>; Thu, 15 Mar 2012 02:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=z/yZPGCdmRT7mVeaBWexlAWhMC2cqwxPCrlIO533L2w=;
        b=INT6+sdZJsvsDO4/WMMGlRqw+JqcQDXKPCSvNxOP8gbNwgzSWZHfTeqh3ztw5XPrw6
         RLRwYnKr3CWpKYTze7/mBscdseUc8UAX5gdfui34AP7H993HxSWCyBFkUhlaQlNfDl0Q
         0Pfdv/iXYeIKWbQZM2syodfE1nsTptMc6LRUL7mdlXjfwvzBCBjItrrPi4zG7xl4ZlFr
         3/0nngPlYL7sjZYxzextlM0e+wPHbFm40NvC1AVb/XmOaAhxJ7me0lbnws1FkLoGXYvu
         j+3tzM77DYE1OnWxJ7ysTmM2zuHmv1pErPEMBnNg/2fvMmDT1ZOvnji1QZ445Tw3Qbmi
         IsFg==
MIME-Version: 1.0
Received: by 10.180.104.65 with SMTP id gc1mr14071336wib.13.1331805178456;
 Thu, 15 Mar 2012 02:52:58 -0700 (PDT)
Received: by 10.217.7.71 with HTTP; Thu, 15 Mar 2012 02:52:58 -0700 (PDT)
Date: Thu, 15 Mar 2012 17:52:58 +0800
Message-ID: 
 <CAF7KpS9E4zW=09V5g5gOdKaY=F55e9p+5A9hQiW6fVVqKJk9xw@mail.gmail.com>
Subject: node exits after it is drained
From: Zhu Han <schumi.han@gmail.com>
To: dev@cassandra.apache.org
Content-Type: multipart/alternative; boundary=f46d043bdb76926ab804bb450eea
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d043bdb76926ab804bb450eea
Content-Type: text/plain; charset=ISO-8859-1

On 1.0.8, the node exits automatically after it is drained, as there is no
non-daemon thread in JVM. But the document said, "after it is drained, it
accepts read requests but not write requests".  Which one is the expected
behavior?

Besides it,  IncomingTcpConnection is not closed when the peer is detected
as dead. The thread might be blocking forever if the peer is down due to
power loss or hard reset. It is a bug?

--f46d043bdb76926ab804bb450eea--