cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6620) Collateral damage from killing a node
Date Sun, 26 Jan 2014 05:27:38 GMT

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

Brandon Williams commented on CASSANDRA-6620:
---------------------------------------------

There are a bunch of tests doing something similar except waiting for the FD here: https://github.com/riptano/cassandra-dtest/blob/master/consistency_test.py

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

Mime
View raw message