[CASSANDRA-12919] Fix inconsistencies in cassandra-stress load balancing policy

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.10
• Component/s: Legacy/Tools
• Severity: Low
• Assignee: Stefania Alborghetti
• Reporter: Stefania Alborghetti

Authors

Stefania Alborghetti

Reviewers

T Jake Luciani

• Created: 17/Nov/16 03:31
• Updated: 16/Apr/19 09:30
• Resolved: 24/Nov/16 01:00

Description

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.