[
https://issues.apache.org/jira/browse/CASSANDRA-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937550#comment-13937550
]
Marcus Eriksson commented on CASSANDRA-6774:
--------------------------------------------
or.. maybe we should return a status code from scrub/upgradesstables/cleanup
instead... i'll fix
> Cleanup fails with assertion error after stopping previous run
> --------------------------------------------------------------
>
> Key: CASSANDRA-6774
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6774
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: 2.0.5
> Reporter: Keith Wright
> Assignee: Marcus Eriksson
> Fix For: 2.0.7
>
> Attachments: 0001-6774-wip.patch,
> 0001-Dont-continue-after-failing-to-cancel-in-progress-co.patch, 6774-v2.txt
>
>
> I am stress testing a new 2.0.5 cluster and did the following:
> - start decommission during heavy write, moderate read load
> - trigger cleanup on non-decommissioning node (nodetool cleanup)
> - Started to see higher GC load stop stopped cleanup via nodetool stop CLEANUP
> - attempt to launch cleanup now fails with the following message in console.
> Cassandra log shows:
> http://aep.appspot.com/display/cKmlMcDuKD72iYAcBykDuVZkRWY/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
