Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of sylvain@datastax.com
 designates 209.85.213.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <loom.20110921T095833-603@post.gmane.org>
References: <loom.20110921T095833-603@post.gmane.org>
From: Sylvain Lebresne <sylvain@datastax.com>
Date: Wed, 21 Sep 2011 10:48:18 +0200
Message-ID: 
 <CAKkz8Q3rEcC7N08Y7Jx1=sy7TMP=kBe=pi=HnBiQNr197vjLcw@mail.gmail.com>
Subject: Re: OutboundTcpConnection in 1.0.0 may stop working
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 21, 2011 at 9:59 AM, liangfeng <liangfeng@made-in-china.com> wrote:
> In cassandra1.0.0, I found that OutboundTcpConnection will throw
> RuntimeException when it encounters an IOException(in write()) .In this case,
> OutboundTcpConnection as a thread will stop working--do not send any message to
> other nodes.
> This is not reasonable,isn't it?

I don't think it is. This was introduced by CASSANDRA-1788 so maybe there was a
good reason for it but I don't see it right away if there is one. This
is likely a mistake.

Do you mind opening a ticket on JIRA for this ?

--
Sylvain