cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12919) Fix inconsistencies in cassandra-stress load balancing policy
Date Thu, 17 Nov 2016 03:50:58 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefania updated CASSANDRA-12919:
---------------------------------
    Fix Version/s:     (was: 3.0.x)

> Fix inconsistencies in cassandra-stress load balancing policy
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-12919
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12919
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Stefania
>            Assignee: Stefania
>            Priority: Minor
>             Fix For: 3.x
>
>
> The default load balancing policy in cassandra-stress is null, which means that the driver
will currently wrap {{DCAwareRoundRobinPolicy}} with {{TokenAwarePolicy}}. 
> However, when a white list of nodes or a data center are specified in the command line
options, then either {{WhiteListPolicy}} or {{DCAwareRoundRobinPolicy}} are used respectively,
without wrapping them in a {{TokenAwarePolicy}}.
> This means that in the default case token aware routing is applied, but in some cases
it is not. Token aware routing could give a performance boost of up to 2.5 times on bare metal,
making comparisons of workloads problematic, if it is applied inconsistently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message