You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2014/01/26 06:11:37 UTC
[jira] [Updated] (CASSANDRA-6620) Collateral damage from killing a
node
[ https://issues.apache.org/jira/browse/CASSANDRA-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated CASSANDRA-6620:
---------------------------------------
Attachment: nodelogs.txt
Trace of the incident.
> 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)