[jira] [Commented] (CASSANDRA-6685) Nodes never bootstrap if schema is empty

["Brandon Williams (JIRA)" <ji...@apache.org>]

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

Brandon Williams commented on CASSANDRA-6685:
---------------------------------------------

Luckily bootstrapping without schema isn't a huge problem or very common, but I propose fixing this by reverting the change in question, since that puts everything back the way it was except for moving the MM events, which solved CASSANDRA-6648.

> Nodes never bootstrap if schema is empty
> ----------------------------------------
>
>                 Key: CASSANDRA-6685
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6685
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Richard Low
>
> Since 1.2.15, bootstrap never completes if the schema is empty. The bootstrapping node endlessly prints:
> bq. {{INFO 12:37:44,863 JOINING: waiting for schema information to complete}}
> until you add something to the schema (i.e. create a keyspace).
> The problem looks to be caused by CASSANDRA-6648, where MigrationManager.isReadForBootstrap() was changed to:
> bq. {{return Schema.instance.getVersion() != null && !Schema.emptyVersion.equals(Schema.instance.getVersion());}}
> This is wrong since {{Schema.emptyVersion.equals(Schema.instance.getVersion())}} is always true if there is no schema.
> We need some different logic for determining when the schema is propagated.
> I haven't tested, but I expect this issue appears in 2.0.5 too.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)