You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2014/12/01 22:03:12 UTC
[jira] [Resolved] (CASSANDRA-8313) cassandra-stress: No way to pass
in data center hint for DCAwareRoundRobinPolicy
[ https://issues.apache.org/jira/browse/CASSANDRA-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani resolved CASSANDRA-8313.
---------------------------------------
Resolution: Not a Problem
> cassandra-stress: No way to pass in data center hint for DCAwareRoundRobinPolicy
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-8313
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8313
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Bob Nilsen
> Assignee: T Jake Luciani
>
> When using cassandra-stress in a multiple datacenter configuration, we need to be able to behave like the applications do and send traffic to nodes co-located in the same data center.
> I can't for the life of me figure out how to pass in such a hint into the new cassandra-stress.
> And passing in a local node into "-node" doesn't help. Apparently, cassandra-stress will *guess* the data center based on the order of the list that it receives from the cluster.
> In my case, it seems to always pick 'DC2', no matter what I do.
> INFO 22:17:06 Using data-center name 'DC2' for DCAwareRoundRobinPolicy (if this is incorrect, please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor)
> Could someone please add the ability to configure the DCAwareRoundRobinPolicy with a data center hint?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)