[ 
https://issues.apache.org/jira/browse/CASSANDRA-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272098#comment-13272098
 ] 

Peter Schuller commented on CASSANDRA-3882:
-------------------------------------------

CASSANDRA-3832 avoided the *gossip* stage being backed up as a result of 
distributed migration manager deadlock, by having the schema rectification be 
executed asynchronously with respect to the gossip stage. This allowed 
bootstrap to complete, among other things ("other things" being anything 
blocking on gossip stage getting to execute incoming tasks).

As indicated in CASSANDRA-3832 
(https://issues.apache.org/jira/browse/CASSANDRA-3832?focusedCommentId=13201012&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13201012)
 there was still the underlying distributed deadlock (or almost deadlock, since 
timeouts allow it to eventually complete) in the migration stage itself.

The posted hack is band-aid for that problem. We're still doing useless work 
performing migration:s beyond what is required, and it doesn't *eliminate* the 
problem - just makes it vastly less likely.
                
> 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

        

Reply via email to