[
https://issues.apache.org/jira/browse/CASSANDRA-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624435#comment-14624435
]
Stefania commented on CASSANDRA-9141:
-------------------------------------
I cannot reproduce it either, I've run it in a loop 10 times. Neither can I
find the string "changes have already been committed" in the source code. I
don't think it was my changes that fixed it however, if anything I would have
thought the sstable lifecycle management fixed this (CASSANDRA-8568).
> Scrub errors when attempting to abort
> -------------------------------------
>
> Key: CASSANDRA-9141
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9141
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Benedict
> Fix For: 3.x
>
>
> On trunk, when scrub attempts to abort, the following error occurs:
> {noformat}
> java.lang.IllegalStateException: Cannot abort - changes have already been
> committed
> at
> org.apache.cassandra.io.sstable.SSTableRewriter.abort(SSTableRewriter.java:195)
> at org.apache.cassandra.db.compaction.Scrubber.scrub(Scrubber.java:277)
> at
> org.apache.cassandra.db.ScrubTest.testScrubCorruptedCounterRow(ScrubTest.java:158)
> {noformat}
> This is reproduceable with the {{ScrubTest.testScrubCorruptedCounterRow()}}
> unit test, although the patch to correctly enable compression from
> CASSANDRA-9135 is required (if it's not committed yet).
> Assigning to [~yukim] for now, since I don't have a better idea of who to
> assign to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
