[
https://issues.apache.org/jira/browse/CASSANDRA-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839888#comment-15839888
]
Chris Lohfink edited comment on CASSANDRA-9639 at 1/26/17 3:44 PM:
-------------------------------------------------------------------
The primary ranges will differ based on the keyspace and replication
strategy/factor. Particularly true of vnode/multi DC environments where the
TokenMetadata.getPredecessor of each local token is not necessarily the bounds
of the primary ranges. patch at https://github.com/clohfink/cassandra/pull/6
was (Author: cnlwsu):
The primary ranges will differ based on the keyspace and replication
strategy/factor. Particularly true of vnode/multi DC environments where the
TokenMetadata.getPredecessor of each local token is not necessarily the bounds
of the primary ranges.
> size_estimates is inacurate in multi-dc clusters
> ------------------------------------------------
>
> Key: CASSANDRA-9639
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9639
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sebastian Estevez
> Assignee: Chris Lohfink
> Priority: Minor
> Fix For: 3.0.x
>
>
> CASSANDRA-7688 introduced size_estimates to replace the thrift
> describe_splits_ex command.
> Users have reported seeing estimates that are widely off in multi-dc clusters.
> system.size_estimates show the wrong range_start / range_end
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
