[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13601279#comment-13601279
]
Ryan McGuire commented on CASSANDRA-5334:
-
[~slebresne], applying your patch and reproducing the steps above I get this in
node2's log (running 1.1.9). The first exception is similar but different,
perhaps another field needs migrating? The second exception I'm not sure if
it's related or needs another ticket.
{code}
ERROR [MigrationStage:1] 2013-03-13 11:57:13,722 AbstractCassandraDaemon.java
(line 135) Exception in thread Thread[MigrationStage:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.utils.ByteBufferUtil.toInt(ByteBufferUtil.java:414)
at org.apache.cassandra.cql.jdbc.JdbcInt32.compose(JdbcInt32.java:98)
at org.apache.cassandra.db.marshal.Int32Type.compose(Int32Type.java:37)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getInt(UntypedResultSet.java:97)
at
org.apache.cassandra.config.CFMetaData.fromSchemaNoColumns(CFMetaData.java:1202)
at
org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1247)
at
org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:299)
at
org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:462)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:374)
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)
ERROR [ReadStage:33] 2013-03-13 11:57:23,794 AbstractCassandraDaemon.java (line
135) Exception in thread Thread[ReadStage:33,5,main]
java.lang.AssertionError: Unknown keyspace system_auth
at org.apache.cassandra.db.Table.init(Table.java:287)
at org.apache.cassandra.db.Table.open(Table.java:119)
at org.apache.cassandra.db.Table.open(Table.java:97)
at
org.apache.cassandra.service.RangeSliceVerbHandler.executeLocally(RangeSliceVerbHandler.java:44)
at
org.apache.cassandra.service.RangeSliceVerbHandler.doVerb(RangeSliceVerbHandler.java:63)
at
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59)
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}
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
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
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13601337#comment-13601337
]
Sylvain Lebresne commented on CASSANDRA-5334:
-
Quick question: does the dtest create new tables in the mixed version cluster?
The last NPE seems related to the old CF id removed by CASSANDRA-3794, however
we still write the old id for column families that have one in 1.2, so in
theory this should only happen if a new column family is created. If that is
the case (that the test create a column family in the mixed version cluster),
then I'm afraid this is not supported between 1.1 and 1.2 (due to
CASSANDRA-3794).
For the 2nd error (the system_auth one), is the dtest doing anything related to
authorization in the mixed version cluster?
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
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] [Commented] (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:comment-tabpanelfocusedCommentId=13601346#comment-13601346
]
Ryan McGuire commented on CASSANDRA-5334:
-
I thought maybe the dtest was doing something I didn't want to have happen, so
I'm not using it for this bug report. The two exceptions in my previous comment
were from issuing ccm commands directly on the command line exactly as I have
in the original report (no dtest used.)
Both exceptions appear in the logs directly after starting the upgraded node.
The only queries issued in this test is the stress command before the upgrade,
no queries were issued after the upgrade.
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
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] [Commented] (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:comment-tabpanelfocusedCommentId=13601470#comment-13601470
]
Jonathan Ellis commented on CASSANDRA-5334:
---
Alternatively, could we hack 1.1.x to ignore the auth CFs?
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] [Commented] (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:comment-tabpanelfocusedCommentId=13601536#comment-13601536
]
Ryan McGuire commented on CASSANDRA-5334:
-
I've tested [~slebresne]'s patch; it works to resolve all the NPEs, assuming
that's the way we want to go. I'm seeing some other issues after the upgrade,
but I'll break those out into separate bugs as I'm pretty sure they're
unrelated to this report.
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] [Commented] (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:comment-tabpanelfocusedCommentId=13601570#comment-13601570
]
Aleksey Yeschenko commented on CASSANDRA-5334:
--
Should MigrationManager.announce() send migrations to 1.1 nodes at all?
{noformat}
// don't send migrations to the nodes with the versions older than
1.1
if (MessagingService.instance().getVersion(endpoint)
MessagingService.VERSION_11)
continue;
{noformat}
Should change it to ' MessagingService.VERSION_12'. Any downsides to it?
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] [Commented] (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:comment-tabpanelfocusedCommentId=13601580#comment-13601580
]
Jonathan Ellis commented on CASSANDRA-5334:
---
That sounds simplest to me, and should fix CASSANDRA-5343. (IIRC we already
have code to prevent 1.1 from pulling the schema from 1.2 nodes, so we just
need to stop 1.2 from pushing it as well.)
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] [Commented] (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:comment-tabpanelfocusedCommentId=13601624#comment-13601624
]
Ryan McGuire commented on CASSANDRA-5334:
-
Tested [~iamaleksey]'s patch fixes all NPEs and resolves this issue. It mostly
fixes CASSANDRA-5343, too, but there is a lingering AsseritionError.
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] [Commented] (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:comment-tabpanelfocusedCommentId=13600264#comment-13600264
]
Brandon Williams commented on CASSANDRA-5334:
-
Do you know which step is causing the exception?
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
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] [Commented] (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:comment-tabpanelfocusedCommentId=13600267#comment-13600267
]
Ryan McGuire commented on CASSANDRA-5334:
-
It only happens once you bring node1 up.
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
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] [Commented] (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:comment-tabpanelfocusedCommentId=13599406#comment-13599406
]
Ryan McGuire commented on CASSANDRA-5334:
-
I've added a
[dtest|https://github.com/riptano/cassandra-dtest/commit/4432c02cc09fb61adce3121a72429132bcc29451]
to test this scenario as well.
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
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.
--
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
