cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Low (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node
Date Tue, 22 Jul 2014 21:56:40 GMT


Richard Low commented on CASSANDRA-5901:

In particular, host replacement can violate consistency, even with CASSANDRA-2434. For example,
if you always do quorum reads and writes and have replicas A, B, C, you'll always read the
latest value, even if any one replica has missed a write. Suppose A did miss a write and then
B fails and is replaced by D. D chooses where to stream from - there is no 'right' answer
- so it can stream from A. Now A and D have old values and only C has the latest value. A
quorum read that chooses A and D will give back stale data and violate expected consistency.

If a repair was run on A and C after B had failed but before it was replaced with D, the consistency
problem is eliminated.

> Bootstrap should also make the data consistent on the new node
> --------------------------------------------------------------
>                 Key: CASSANDRA-5901
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Priority: Minor
> Currently when we are bootstrapping a new node, it might bootstrap from a node which
does not have most upto date data. Because of this, we need to run a repair after that.
> Most people will always run the repair so it would help if we can provide a parameter
to bootstrap to run the repair once the bootstrap has finished. 
> It can also stop the node from responding to reads till repair has finished. This could
be another param as well. 

This message was sent by Atlassian JIRA

View raw message