You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/03/28 21:13:45 UTC

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McGuire updated CASSANDRA-6685:
------------------------------------

    Reproduced In: 2.0.5, 1.2.15  (was: 1.2.15)

> 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
>            Assignee: Brandon Williams
>             Fix For: 1.2.16
>
>
> 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.2#6252)