You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sandeep Tata (JIRA)" <ji...@apache.org> on 2009/05/07 21:58:45 UTC
[jira] Updated: (CASSANDRA-140) allow user to specify how many
nodes to block for on reads and writes
[ https://issues.apache.org/jira/browse/CASSANDRA-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandeep Tata updated CASSANDRA-140:
-----------------------------------
Attachment: CASSANDRA-140-storage.patch
Part1: makes the changes needed in the StorageProxy and the QuorumResponseHandler to admit # of nodes to block on.
I haven't added any new unit tests -- any ideas?
I'll put the thrift interface related changes in part2 and attach.
> allow user to specify how many nodes to block for on reads and writes
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-140
> URL: https://issues.apache.org/jira/browse/CASSANDRA-140
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Sandeep Tata
> Fix For: 0.4
>
> Attachments: CASSANDRA-140-storage.patch
>
>
> currently you only have block for zero (or one, on reads) or quorum. block for one (on writes), and all are also useful values. allow user to specify this as a number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.