cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6620) Collateral damage from killing a node
Date Sun, 26 Jan 2014 17:14:37 GMT


Brandon Williams commented on CASSANDRA-6620:

bq. According to the CQL docs the default consistency level is ONE

Not if you're passing it over thrift, which obviously requires the parameter passed outside
of the query.

bq. I have set it to ALL

Why?  This is certainly going to fail with either TOE before the FD sees it, or UE after it

> Collateral damage from killing a node
> -------------------------------------
>                 Key: CASSANDRA-6620
>                 URL:
>             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

View raw message