[
https://issues.apache.org/jira/browse/CASSANDRA-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905898#comment-13905898
]
Robert Coli commented on CASSANDRA-6685:
----------------------------------------
{quote}Luckily bootstrapping without schema isn't a huge problem or very
common{quote}
In every cluster I have ever run, my initial setup process goes :
1) coalesce cluster
2) load schema
The above process seems "very common" to me; I am surprised to hear suggestion
that anyone ever does anything else. A bug such as this one which would affect
most noobs setting up My First Cassandra Cluster also seems "very common" to
me, and a "huge problem."
In my view, this bug is serious enough to warrant an accelerated 1.2.16 release
schedule.
> 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.1.5#6160)
