cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Meyer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5844) NullPointer exception running upgrade_through_versions_test dtest
Date Wed, 07 Aug 2013 20:37:48 GMT

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

Daniel Meyer commented on CASSANDRA-5844:
-----------------------------------------

>From my testing I am consistently seeing the error in upgrading from 1.2 -> trunk.
 The logs are a bit confusing to read; however I have added a check to look for the error
after every upgrade that occurs in my local version of the test.

I consistently see the following behavior in the mixed version test (there are three nodes
in the cluster):

upgrade node1 from 1.2 -> trunk -- Successful
upgrade node2 and node3 from 1.2 -> Trunk -- Fails with NPE in the logs of node3 every
time

The problem seems to occur 50% of the time, with successful runs generally lumped together.
 It seems like 4-5 runs will fail followed by 4-5 successful runs.  These numbers are variable
though and the behavior is random.

                
> NullPointer exception running upgrade_through_versions_test dtest
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-5844
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5844
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.9
>         Environment: java version "1.7.0_25"
> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
>            Reporter: Daniel Meyer
>         Attachments: node1.log, node2.log, node3.log
>
>
> This error is observed while running upgrade_through_versions_test.  Specifically the
error occurs going from 1.2 -> trunk:
> ERROR: Only upgrade part of the cluster, so we have mixed versions when
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/Users/danielmeyer/Sources/riptano/cassandra-dtest/dtest.py", line 145, in tearDown
>     raise AssertionError('Unexpected error in %s node log: %s' % (node.name, errors))
> AssertionError: Unexpected error in node3 node log: ['ERROR [MigrationStage:1] 2013-08-02
15:12:13,647 CassandraDaemon.java (line 192) Exception in thread Thread[MigrationStage:1,5,main]\n']
> The exception found in logs (node3) is as follows:
> java.lang.NullPointerException
>     at org.apache.cassandra.db.DefsTable.addColumnFamily(DefsTable.java:510)
>     at org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:444)
>     at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:354)
>     at org.apache.cassandra.db.DefinitionsUpdateVerbHandler$1.runMayThrow(DefinitionsUpdateVerbHandler.java:55)
>     at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
>     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>     at java.lang.Thread.run(Thread.java:724)

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

Mime
View raw message