cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Low (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6685) Nodes never bootstrap if schema is empty
Date Mon, 10 Feb 2014 15:04:22 GMT


Richard Low commented on CASSANDRA-6685:

Wasn't this change made to guard against the case when schema messages get delayed and responses
aren't received before bootstrap begins?

> Nodes never bootstrap if schema is empty
> ----------------------------------------
>                 Key: CASSANDRA-6685
>                 URL:
>             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

View raw message