cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
Date Mon, 11 Mar 2013 22:25:12 GMT
Ryan McGuire created CASSANDRA-5334:

             Summary: NullPointerException in a mixed 1.1 / 1.2 cluster
                 Key: CASSANDRA-5334
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.1.9
            Reporter: Ryan McGuire

I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 node upgraded from

The upgrade works, and I don't see any problems end user problems, however I see this exception
in the logs on the non-upgraded nodes:

ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 (line 135) Exception
in thread Thread[MigrationStage:1,5,main]
	at org.apache.cassandra.utils.ByteBufferUtil.string(
	at org.apache.cassandra.utils.ByteBufferUtil.string(
	at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(
	at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(
	at org.apache.cassandra.db.marshal.UTF8Type.compose(
	at org.apache.cassandra.cql3.UntypedResultSet$Row.getString(
	at org.apache.cassandra.config.KSMetaData.fromSchema(
	at org.apache.cassandra.db.DefsTable.mergeKeyspaces(
	at org.apache.cassandra.db.DefsTable.mergeSchema(
	at org.apache.cassandra.db.DefsTable.mergeRemoteSchema(
	at org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(
	at java.util.concurrent.Executors$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

Steps to reproduce:
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 down

edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2

ccm node1 up

The cluster is now a mixed version, and works for user queries, but with the exception above.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message