[
https://issues.apache.org/jira/browse/CASSANDRA-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661405#comment-14661405
]
Chris Moos commented on CASSANDRA-10008:
----------------------------------------
I think I may have tracked down the issue, it seems that this happens because
sstables from the old version and new version both exist in the transaction and
during upgrade cancel() is used to filter out the latest versions sstables, but
cancel() is not fully removing the SSTableReader from the transaction.
Patch attached.
> Upgrading SSTables fails on 2.2.0 (after upgrade from 2.1.2)
> ------------------------------------------------------------
>
> Key: CASSANDRA-10008
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10008
> Project: Cassandra
> Issue Type: Bug
> Reporter: Chris Moos
> Fix For: 2.2.x
>
>
> Running *nodetool upgradesstables* fails with the following after upgrading
> to 2.2.0 from 2.1.2:
> {code}
> error: null
> -- StackTrace --
> java.lang.AssertionError
> at
> org.apache.cassandra.db.lifecycle.LifecycleTransaction.checkUnused(LifecycleTransaction.java:428)
> at
> org.apache.cassandra.db.lifecycle.LifecycleTransaction.split(LifecycleTransaction.java:408)
> at
> org.apache.cassandra.db.compaction.CompactionManager.parallelAllSSTableOperation(CompactionManager.java:268)
> at
> org.apache.cassandra.db.compaction.CompactionManager.performSSTableRewrite(CompactionManager.java:373)
> at
> org.apache.cassandra.db.ColumnFamilyStore.sstablesRewrite(ColumnFamilyStore.java:1524)
> at
> org.apache.cassandra.service.StorageService.upgradeSSTables(StorageService.java:2521)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
