You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robbie Strickland (JIRA)" <ji...@apache.org> on 2014/05/20 17:08:41 UTC
[jira] [Commented] (CASSANDRA-7252) RingCache cannot be configured
to use local DC only
[ https://issues.apache.org/jira/browse/CASSANDRA-7252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003408#comment-14003408 ]
Robbie Strickland commented on CASSANDRA-7252:
----------------------------------------------
[~iamaleksey] I see you changed the fix version to 2.0.9. Do you want me to rebase the patch?
> RingCache cannot be configured to use local DC only
> ---------------------------------------------------
>
> Key: CASSANDRA-7252
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7252
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Reporter: Robbie Strickland
> Assignee: Jonathan Ellis
> Labels: patch
> Fix For: 2.0.9
>
> Attachments: cassandra-2.0.7-7252-2.txt, cassandra-2.0.7-7252.txt
>
>
> RingCache always calls describe_ring, returning the entire cluster. Considering it's used in the context of writing from Hadoop (which is typically in a multi-DC configuration), this is often not desirable behavior. In some cases there may be high-latency connections between the analytics DC and other DCs.
> I am attaching a patch that adds an optional config value to tell RingCache to use local nodes only, in which case it calls describe_local_ring instead. It also adds helpful failed host information to IOExceptions thrown in AbstractColumnFamilyOutputFormat.createAuthenticatedClient, CqlRecordWriter, and ColumnFamilyRecordWriter. This allows a user to more easily solve related connectivity issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)