cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Priscornic (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13957) upgradesstables fails after upgrading from 2.1.x to 3.0.14
Date Mon, 16 Oct 2017 10:34:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Priscornic updated CASSANDRA-13957:
---------------------------------------
    Summary: upgradesstables fails after upgrading from 2.1.x to 3.0.14  (was: upgradesstables
fails after upgrading from 2.1.x to 3.0.11)

> upgradesstables fails after upgrading from 2.1.x to 3.0.14
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-13957
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13957
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Dan Priscornic
>
> After upgrading DSE from 4.8.14 (cassandra 2.1.18.1463) to 5.0.10 (cassandra 3.0.14.1862)
I ran nodetool upgradesstables and it fails with the following stack trace:
> {code:java}
> # nodetool -u cassandra -pwf /etc/dse/cassandra/jmxremote.password upgradesstables
> error: null
> -- StackTrace --
> java.lang.AssertionError
> 	at org.apache.cassandra.db.rows.Rows.collectStats(Rows.java:70)
> 	at org.apache.cassandra.io.sstable.format.big.BigTableWriter$StatsCollector.applyToRow(BigTableWriter.java:197)
> 	at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:137)
> 	at org.apache.cassandra.db.ColumnIndex$Builder.build(ColumnIndex.java:111)
> 	at org.apache.cassandra.db.ColumnIndex.writeAndBuildIndex(ColumnIndex.java:52)
> 	at org.apache.cassandra.io.sstable.format.big.BigTableWriter.append(BigTableWriter.java:149)
> 	at org.apache.cassandra.io.sstable.SSTableRewriter.append(SSTableRewriter.java:125)
> 	at org.apache.cassandra.db.compaction.writers.DefaultCompactionWriter.realAppend(DefaultCompactionWriter.java:57)
> 	at org.apache.cassandra.db.compaction.writers.CompactionAwareWriter.append(CompactionAwareWriter.java:109)
> 	at org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:205)
> 	at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> 	at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:99)
> 	at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:61)
> 	at org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:427)
> 	at org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:314)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:79)
> 	at org.apache.cassandra.concurrent.NamedThreadFactory$$Lambda$6/61137731.run(Unknown
Source)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}
> The bug seems similar to CASSANDRA-13320 which says it should be fixed in cassandra 3.0.11
but does not look fixed in 3.0.14



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message