[
https://issues.apache.org/jira/browse/CASSANDRA-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Capriolo reopened CASSANDRA-6620:
----------------------------------------
It is a problem. Writes at ONE should not timeout with RF=2 cluster=3 and only
one node down. The user should not have to re-try this write operation.
> 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)
