Yeah, looks like it should just pass through to where writeConnected can handle it more gracefully like it did pre-1788.
On Wed, Sep 21, 2011 at 3:48 AM, Sylvain Lebresne <sylv...@datastax.com> wrote: > On Wed, Sep 21, 2011 at 9:59 AM, liangfeng <liangf...@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 > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
