cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Low (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6685) Nodes never bootstrap if schema is empty
Date Thu, 13 Feb 2014 16:46:20 GMT

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

Richard Low commented on CASSANDRA-6685:
----------------------------------------

Here's the git commit:

https://github.com/apache/cassandra/commit/c5627008a2c87ab960da98f4d5b8ca4aca6eebdd

> 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)

Mime
View raw message