[
https://issues.apache.org/jira/browse/CASSANDRA-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272367#comment-13272367
]
Jonathan Ellis commented on CASSANDRA-3882:
-------------------------------------------
Quoting from 3832: "[the deadlock] is because all nodes, when a node is marked
alive, just know that it has a different schema - not who has the "newer"
schema. So when a node joins it gets migration messages from others while it
also tries to send migration messages to others and waiting on the response.
Whenever it sends a migration message to someone whose migration stage is busy
waiting on a response from the node in question - deadlock (until timeout)."
> avoid distributed deadlock in migration stage
> ---------------------------------------------
>
> Key: CASSANDRA-3882
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3882
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Peter Schuller
> Assignee: Peter Schuller
> Attachments: CASSANDRA-3882-hack.txt
>
>
> This is follow-up work for the remainders of CASSANDRA-3832 which was only a
> partial fix. The deadlock in the migration stage needs to be fixed, as it can
> cause bootstrap (at least) to take potentially a very very long time to
> complete, and might also cause a lack of schema propagation until otherwise
> "poked".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
