You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/10/17 00:43:31 UTC
[jira] Updated: (CASSANDRA-497) Include bootstrap targets in
consistencylevel computations
[ https://issues.apache.org/jira/browse/CASSANDRA-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-497:
-------------------------------------
Attachment: 0002-make-write-targets-computable-independent-of-replicati.txt
0001-CASSANDRA-497-rename-nodePicker-replicationStrategy.txt
> 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.