cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-497) Include bootstrap targets in consistencylevel computations
Date Thu, 22 Oct 2009 12:35:59 GMT


Hudson commented on CASSANDRA-497:

Integrated in Cassandra #235 (See [])
    Make EndPoint objects immmutable, so hashcode can't change (making the EndPoint potentially
disappear from a map)
patch by jbellis; reviewed by Sandeep Tata for 
make write targets computable independent of replication strategy (i.e., make getReadStorageEndPoints
the only method a Strategy needs to implement).  we do this by computing the token/endpoint
-> Range[] map from the read endpoints, then using that to determine if a bootstrapping
node needs to receive a write (if the token being written falls in any of its ranges).  Also,
make the StorageProxy insert methods aware that bootstrap can entail having extra write targets
temporarily, and include those in its consistencylevel calculations.
patch by jbellis; reviewed by Sandeep Tata for 
rename nodePicker -> replicationStrategy.
patch by jbellis; reviewed by Sandeep Tata for 

> Include bootstrap targets in consistencylevel computations
> ----------------------------------------------------------
>                 Key: CASSANDRA-497
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>         Attachments: 0001-CASSANDRA-497-rename-nodePicker-replicationStrategy.txt, 0002-make-write-targets-computable-independent-of-replicati.txt,
0003-Make-EndPoint-objects-immmutable-so-hashcode-can-t-ch.txt, imports.patch
> We want to preserve ConsistencyLevel semantics during bootstrap, and if a CL.quorum/all
write is sent to a bootstrap target, it would have to wait for the forwarded write to complete
to report in turn that the write is good.
> Leaving write propagation to be done by the write originator means we don't have this
extra layer of latency.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message