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 2017/01/03 18:07:58 UTC
[jira] [Updated] (CASSANDRA-13074) DynamicEndpointSnitch frequently
no-ops through early exit in multi-datacenter situations
[ https://issues.apache.org/jira/browse/CASSANDRA-13074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani updated CASSANDRA-13074:
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.x)
(was: 3.0.x)
(was: 2.2.x)
(was: 3.x)
3.10
3.0.11
2.2.9
Status: Resolved (was: Patch Available)
Great thanks! +1 committed {{e4f732536af9d81dd012d7d498b884cd7c8c0b48}}
> DynamicEndpointSnitch frequently no-ops through early exit in multi-datacenter situations
> -----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13074
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13074
> Project: Cassandra
> Issue Type: Bug
> Components: Coordination
> Reporter: Joel Knighton
> Assignee: Joel Knighton
> Fix For: 2.2.9, 3.0.11, 3.10
>
>
> The DynamicEndpointSnitch attempts to use timings from nodes to route reads to better performing nodes.
> In a multi-datacenter situation, timings will likely be empty for nodes outside of the local datacenter, as you'll frequently only be doing local_quorum reads (or a lower consistency level). In this case, the DES exits early and returns the subsnitch ordering. This means poorly performing replicas will never be avoided, no matter how degraded they are.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)