cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-6740) Non-empty flush directory causes NPE on startup
Date Wed, 19 Feb 2014 21:06:19 GMT
Ryan McGuire created CASSANDRA-6740:

             Summary: Non-empty flush directory causes NPE on startup
                 Key: CASSANDRA-6740
             Project: Cassandra
          Issue Type: Bug
            Reporter: Ryan McGuire
            Priority: Minor

With the changes in CASSANDRA-6357, there is now the case where someone may want to start
a fresh cluster on a machine that previously hosted one, clean out the directories they are
familiar with (eg, data_file_directories, commitlog_directories) but fail to clean out the
flush_directory. If they don't clean that out, they will see this in the logs:

INFO  [main] 2014-02-19 12:20:13,530 - Initializing system.IndexInfo
INFO  [main] 2014-02-19 12:20:13,534 - Initializing system.peers
INFO  [main] 2014-02-19 12:20:13,539 - Initializing system.local
ERROR [main] 2014-02-19 12:20:13,703 - Exception encountered during
java.lang.NullPointerException: null
        at org.apache.cassandra.utils.ByteBufferUtil.string( ~[main/:na]
        at org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(
        at org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(
        at org.apache.cassandra.db.marshal.AbstractType.compose( ~[main/:na]
        at org.apache.cassandra.cql3.UntypedResultSet$Row.getString(
        at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(
        at org.apache.cassandra.config.CFMetaData.fromSchema( ~[main/:na]
        at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(
        at org.apache.cassandra.config.KSMetaData.fromSchema( ~[main/:na]
        at org.apache.cassandra.db.DefsTables.loadFromKeyspace( ~[main/:na]
        at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(
        at org.apache.cassandra.service.CassandraDaemon.setup( [main/:na]
        at org.apache.cassandra.service.CassandraDaemon.activate(
        at org.apache.cassandra.service.CassandraDaemon.main( [main/:na]

I suggest a better warning message telling them it's due to the unclean flush dir, instead
of an NPE.

This message was sent by Atlassian JIRA

View raw message