cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5612) NPE when upgrading a mixed version 1.1/1.2 cluster fully to 1.2
Date Tue, 04 Jun 2013 02:57:19 GMT
Ryan McGuire created CASSANDRA-5612:

             Summary: NPE when upgrading a mixed version 1.1/1.2 cluster fully to 1.2
                 Key: CASSANDRA-5612
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.6
            Reporter: Ryan McGuire
         Attachments: logs.tar.gz,

See the attached upgrade_test_mixed().

Conceptually this method does the following:

* Instantiates a 3 node 1.1.9 cluster
* Writes some data
* Shuts down node 1 and upgrades it to 1.2 (HEAD)
* Brings the node1 back up, making a the cluster a mixed version 1.1/1.2
* Brings down node2 and node3 and does the same upgrade making it all the same version.
* At this point, I would run upgradesstables on each of the nodes, but there is already an
error on node3 directly after it's upgrade:

INFO [FlushWriter:1] 2013-06-03 22:49:46,543 (line 461) Writing Memtable-peers@1023263314(237/237
serialized/live bytes, 14 op
 INFO [FlushWriter:1] 2013-06-03 22:49:46,556 (line 495) Completed flushing
em-peers-ic-2-Data.db (291 bytes) for commitlog position ReplayPosition(segmentId=1370314185862,
 INFO [GossipStage:1] 2013-06-03 22:49:46,568 (line 1330) Node /
state jump to normal
ERROR [MigrationStage:1] 2013-06-03 22:49:46,655 (line 192) Exception
in thread Thread[MigrationStage:1,5,main]
        at org.apache.cassandra.db.DefsTable.addColumnFamily(
        at org.apache.cassandra.db.DefsTable.mergeColumnFamilies(
        at org.apache.cassandra.db.DefsTable.mergeSchema(
        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.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

This error is repeatable, but inconsistent. Interestingly, it is always node3 with the error.

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