[
https://issues.apache.org/jira/browse/CASSANDRA-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272435#comment-13272435
]
Peter Schuller commented on CASSANDRA-3882:
-------------------------------------------
I'm not sure what your intention is with the quote. If you mean that it implies
it's only during bootstrap, it's because I was only considering bootstrap at
the time and didn't think far enough to realize this would be a problem in
general for schema changes.
The empirical observation is that all nodes are stuck with lots of
migrationstage pending, schema requests time out, schema updates at CLI sit
there forever, and it very very very slowly recovers since each guy is waiting
on RPC timeout (depending on said timeout).
jstacking shows waiting in the migration stage on that future, for a response.
> 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
