[
https://issues.apache.org/jira/browse/CASSANDRA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563161#comment-13563161
]
Jonathan Ellis commented on CASSANDRA-3899:
-------------------------------------------
I think this was fixed by the vnodes TM rewrite. In any case
TM.getWriteEndpoints still exists but is only used by tests now.
> TM.getWriteEndpoints() is linear in number of pending ranges
> ------------------------------------------------------------
>
> Key: CASSANDRA-3899
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3899
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Peter Schuller
> Assignee: Peter Schuller
>
> Despite the comment of the method, it's not just being used by replication
> strategies; it's being used in {{StorageProxy.getWriteEndpoints{}}} in the
> write patch.
> This matters because the minimum number of nodes to be bootstrapping into a
> cluster at once in order to finish a capacity add in a reasonable period,
> scales linearly with cluster size. We don't want per-request costs to scale
> linearly with cluster size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
