[
https://issues.apache.org/jira/browse/CASSANDRA-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867651#action_12867651
]
Jeremy Hanna commented on CASSANDRA-952:
----------------------------------------
Cool - yeah - looking at it again, DSS contains DC RF information for all
keyspaces, so it really wouldn't matter if it was a singleton for all keyspaces.
Btw, I was mostly just reviewing the getNaturalEndpointsInternal method of DSS
- Jonathan had asked me to take a look at it in IRC. Just so you know I wasn't
reviewing the entire patch. I don't know if that matters too much, but thought
I would clarify.
> 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, 0.8
>
> Attachments:
> 0001-clean-out-callback-purging-from-truncate-writerh.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-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.
