[
https://issues.apache.org/jira/browse/CASSANDRA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868642#action_12868642
]
Hudson commented on CASSANDRA-952:
----------------------------------
Integrated in Cassandra #439 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/439/])
make DCQUORUM CLs actually wait for the nodes per DC rather than attempting
a purely count-based approach that didn't really work as advertised. patch by
Vijay Parthasarathy and jbellis; reviewed by Jeremy Hanna for CASSANDRA-952
> DC Quorum broken @ trunk
> ------------------------
>
> Key: CASSANDRA-952
> URL: https://issues.apache.org/jira/browse/CASSANDRA-952
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.6
> Environment: Linux, Cassandra
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.7
>
> Attachments:
> 0001-clean-out-callback-purging-from-truncate-writerh.txt,
> 0002-dcquorum-fixes-v2.txt, 0002-dcquorum-fixes.txt,
> 952-Canges_To_Stategy_V002.txt, 952-Change_BlockFor.txt,
> 952-Changes_To_ResponseHandler_v002.txt, 952-Fix_Refactor_DCStatergy.txt,
> 952-v3.txt, 952-v3.txt, 952-v4.txt, 952-v4.txt, 952-v5.txt, DC-Config.xml
>
>
> Currently DCQuorum is broken in trunk, Suggesting the following fix...
> Write to DC's
> 1) Move determineBlockFor(int expandedTargets, ConsistencyLevel
> consistency_level) to AbstractEndpointSnitch
> 2) Add the same to support DC Quorum in DatacenterShardStategy
> Read to DC's
> 1) find suitable nodes was a list which was returning a list of local DC's
> earlier but now it is just one node and MD is been sent by other nodes. Need
> to have an option to even avoid MD from other DC's?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
