[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5334:
Attachment: 5334.txt
This was introduced by CASSANDRA-4433, that removed the name column of the
schema_keyspaces table, but that one, while redundant, is used by 1.1 nodes.
This boils down to the problem I described in CASSANDRA-4603: we cannot easily
remove anything in the schema tables without breaking rolling upgrades.
So attaching a patch that reintroduce the name column in 1.2 (we don't use it
but we write it for compatibility sake).
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Attachments: 5334.txt
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 down
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
{code}
ccm node1 up
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5334:
Fix Version/s: 1.2.3
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Fix For: 1.2.3
Attachments: 5334.txt
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 down
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
{code}
ccm node1 up
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McGuire updated CASSANDRA-5334:
Description:
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 node
upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
The cluster is now a mixed version, and works for user queries, but with the
exception above.
was:
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 node
upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 down
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
{code}
ccm node1 up
{code}
The cluster is now a mixed version, and works for user queries, but with the
exception above.
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project:
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McGuire updated CASSANDRA-5334:
Attachment: cassandra.trunk.yaml
The cassandra.yaml for the 1.1.9 nodes are the default that ccm creates.
Attached is my cassandra.yaml that I use for the upgraded node. This is
basically the default one that ccm creates for 1.2.2 modified to use the
RandomPartitioner that the node is using and some path fixes.
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: 5334.txt, cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5334:
Attachment: (was: 5334.txt)
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5334:
Attachment: 5334.txt
Alright. The problem is that due to CASSANDRA-3794 (and to a lower extend
CASSANDRA-4433), new keyspaces/column families cannot be created in a mixed
1.1/1.2 cluster (keyspace lacks the name column and column families lack an
old-style CfId).
This is a limitation we accepted in CASSANDRA-3794, but unfortunately, 1.2
creates the system_auth keyspace/column families on startup if they don't exist
which triggers pretty much all the stacktrace on this issue.
One hacky solution I can see is to 1) reintroduce the name column for
keyspace, and 2) we manually provide an old-style cfId for the Auth.USERS_CF.
Attaching an updated patch that does both. This is ugly however.
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5334:
Attachment: (was: 5334.txt)
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-5334:
Attachment: 5334.patch
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: 5334.patch, cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McGuire updated CASSANDRA-5334:
Tester: enigmacurry
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: 5334.patch, cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-5334:
-
Attachment: 5334.txt
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: 5334.patch, 5334.txt, cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-5334:
-
Attachment: (was: 5334.txt)
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: 5334.patch, 5334-v2.txt, cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-5334:
-
Attachment: 5334-v2.txt
v2 prevents 1.2 nodes from pushing migrations to 1.1 nodes.
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ryan McGuire
Assignee: Sylvain Lebresne
Fix For: 1.2.3
Attachments: 5334.patch, 5334-v2.txt, cassandra.trunk.yaml
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2
node upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 stop
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2.
Edit node1's cassandra.yaml to be 1.2 compliant.
{code}
ccm node1 start
{code}
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: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5334) NullPointerException in a mixed 1.1 / 1.2 cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McGuire updated CASSANDRA-5334:
Description:
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 node
upgraded from 1.1.9.
The upgrade works, and I don't see any end user problems, however I see this
exception in the logs on the non-upgraded nodes:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 down
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
{code}
ccm node1 up
{code}
The cluster is now a mixed version, and works for user queries, but with the
exception above.
was:
I have a mixed version cluster consisting of two 1.1.9 nodes and one 1.2.2 node
upgraded from 1.1.9.
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:
{code}
ERROR [MigrationStage:1] 2013-03-11 18:09:09,001 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:167)
at
org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:124)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
at org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
at org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
at
org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:256)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:397)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:373)
at
org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:352)
at
org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:48)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{code}
Steps to reproduce:
{code}
ccm create -v 1.1.9 1.1.9
ccm populate -n 3
ccm start
ccm node1 stress
ccm node1 down
{code}
edit ~/.ccm/1.1.9/cluster.conf and configure cassandra_dir to point to 1.2.2
{code}
ccm node1 up
{code}
The cluster is now a mixed version, and works for user queries, but with the
exception above.
NullPointerException in a mixed 1.1 / 1.2 cluster
-
Key: CASSANDRA-5334
URL: https://issues.apache.org/jira/browse/CASSANDRA-5334
Project: Cassandra
Issue Type: Bug
