[ https://issues.apache.org/jira/browse/CASSANDRA-14801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075318#comment-17075318 ]
Benedict Elliott Smith commented on CASSANDRA-14801: ---------------------------------------------------- bq. Please refrain from focusing on who is employed by whom and instead focus on their individual merit and contribution to the code-base in the future. It is the case that new contributors can generally be assumed to have no knowledge of complex areas of the codebase. There is however precisely one company I am aware of with people who may secretly have the requisite knowledge and skill. There is also only one company with _full time_ contributors that were previously unknown to the community, who may have the time to either obtain the necessary skill, or to have weeks to dedicate to difficult tasks such as this. Were this to be a random individual, I could quite reasonably just direct them to another ticket. In this case I thought it was best only to issue a fair warning that this _might_ not be suitable but that I do not have sufficient knowledge to say for sure. I am perceiving a pattern on your part, of choosing to interpret my actions in an unwarrantedly negative light. Please check yourself, before you check others. > calculatePendingRanges no longer safe for multiple adjacent range movements > --------------------------------------------------------------------------- > > Key: CASSANDRA-14801 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14801 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Coordination, Legacy/Distributed Metadata > Reporter: Benedict Elliott Smith > Assignee: Aleksandr Sorokoumov > Priority: Normal > Labels: pull-request-available > Fix For: 4.0, 4.0-beta > > Time Spent: 10m > Remaining Estimate: 0h > > Correctness depended upon the narrowing to a {{Set<InetAddressAndport>}}, > which we no longer do - we maintain a collection of all {{Replica}}. Our > {{RangesAtEndpoint}} collection built by {{getPendingRanges}} can as a result > contain the same endpoint multiple times; and our {{EndpointsForToken}} > obtained by {{TokenMetadata.pendingEndpointsFor}} may fail to be constructed, > resulting in cluster-wide failures for writes to the affected token ranges > for the duration of the range movement. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org