[
https://issues.apache.org/jira/browse/CASSANDRA-15224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886472#comment-16886472
]
Joseph Lynch commented on CASSANDRA-15224:
------------------------------------------
This is at least fixed in the trunk patch for CASSANDRA-14459. I may be able to
isolate those changes for backport to the 3.x series.
> DynamicSnitch.applyConfigChanges can corrupt snitch state
> ---------------------------------------------------------
>
> Key: CASSANDRA-15224
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15224
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
> Reporter: Benedict
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> This method is not synchronised, and doesn’t wait for the cancelled task to
> complete (which could already be running), so we could have two updates in
> flight simultaneously and corrupt the internal state of the collection
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
