[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219012#comment-15219012
]
Yuki Morishita commented on CASSANDRA-8616:
-------------------------------------------
Progress update: There are several places other than
{{system.sstable_activity}} that offline tools access(vary by version). Trying
to patch everything, otherwise tools can hang (dtest is catching these).
* In cassandra-2.2, offline tools (sstablesplit and posssibly other few) can
update {{system.compaction_in_progress}} and {{system.compaction_history}}.
* In cassandra-3.0+, sstablescrub against secondary index sstables can update
{{system.IndexInfo}}.
> sstable tools may result in commit log segments be written
> ----------------------------------------------------------
>
> Key: CASSANDRA-8616
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8616
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Tyler Hobbs
> Assignee: Yuki Morishita
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
> Attachments: 8161-2.0.txt
>
>
> There was a report of sstable2json causing commitlog segments to be written
> out when run. I haven't attempted to reproduce this yet, so that's all I
> know for now. Since sstable2json loads the conf and schema, I'm thinking
> that it may inadvertently be triggering the commitlog code.
> sstablescrub, sstableverify, and other sstable tools have the same issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
