isReadyForBootstrap doesn't compare schema UUID by timestamp as it should
-------------------------------------------------------------------------
Key: CASSANDRA-4159
URL: https://issues.apache.org/jira/browse/CASSANDRA-4159
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.7
Reporter: Sylvain Lebresne
Fix For: 1.0.10
CASSANDRA-3629 introduced a wait to be sure the node is up to date on the
schema before starting bootstrap. However, the isReadyForBootsrap() method
compares schema version using UUID.compareTo(), which doesn't compare UUID by
timestamp, while the rest of the code does compare using timestamp
(MigrationManager.updateHighestKnown).
During a test where lots of node were boostrapped simultaneously (and some
schema change were done), we ended up having some node stuck in the
isReadyForBoostrap loop. Restarting the node fixed it, so while I can't confirm
it, I suspect this was the source of that problem.
--
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