[
https://issues.apache.org/jira/browse/CASSANDRA-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882344#comment-13882344
]
Edward Capriolo edited comment on CASSANDRA-6620 at 1/26/14 4:41 PM:
---------------------------------------------------------------------
According to the CQL docs the default consistency level is ONE. Look at the
exception:
{quote}
TimedOutException(acknowledged_by:0)
{quote}
acknoledged_by:0 shows that of the natural endpoints for the key it was writing
to increment, one was down, the other should have responded. It is not a socket
time out, so a GC does not explain. It is an application level time out.
was (Author: appodictic):
According to the CQL docs the default consistency level is ONE. Look at the
exception:
{quote}
TimedOutException(acknowledged_by:0)
{quote}
acknoledged_by:0 shows that of the two replicas, one was down, the other should
have responded. It is not a socket time out, so a GC does not explain. It is an
application level time out.
> Collateral damage from killing a node
> -------------------------------------
>
> Key: CASSANDRA-6620
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6620
> Project: Cassandra
> Issue Type: Bug
> Reporter: Edward Capriolo
> Attachments: nodelogs.txt
>
>
> I have designed a new scenario with farsandra:
> 3 nodes with Replication factor = 2 a Counter column family. I perform 10,000
> inserts to node 1. I kill off node 2, do 10000 more inserts. restart node 2.
> Sometimes I made it completely though this test. However sometimes I do not.
> I have seen the client throw time out exceptions. it seems like the death of
> node 2 greatly upsets node 1 and it times out a request. Since the default is
> ready 1 should this be happening?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
