Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 26 Jan 2014 16:22:37 +0000 (UTC)
From: "Edward Capriolo (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12691244.1390712942168.15607.1390753357635@arcas>
In-Reply-To: <JIRA.12691244.1390712942168@arcas>
References: <JIRA.12691244.1390712942168@arcas>
Subject: [jira] [Commented] (CASSANDRA-6620) Collateral damage from killing
 a node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882334#comment-13882334 ] 

Edward Capriolo commented on CASSANDRA-6620:
--------------------------------------------

Why resolve this? It is a problem I think. Cassandra should not time out in this scenario?

> 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)