[jira] Commented: (CASSANDRA-497) Include bootstrap targets in consistencylevel computations

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-497:
------------------------------------------

patch:

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.

> Include bootstrap targets in consistencylevel computations
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-497
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-497
>             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
>
>
> 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.