https://issues.apache.org/jira/browse/CASSANDRA-3235
On Wed, Sep 21, 2011 at 4:34 AM, liangfeng wrote:
>> Do you mind opening a ticket on JIRA for this ?
>
> Yes,if it is a mistake. Thanks!
>
>
>
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for profe
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 wrote:
> On Wed, Sep 21, 2011 at 9:59 AM, liangfeng
> wrote:
>> In cassandra1.0.0, I found that OutboundTcpConnection will t
> Do you mind opening a ticket on JIRA for this ?
Yes,if it is a mistake. Thanks!
On Wed, Sep 21, 2011 at 9:59 AM, liangfeng 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.
>
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?
