[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154523#comment-15154523
]
Yuki Morishita commented on CASSANDRA-8616:
-------------------------------------------
Bad news. My approach didn't work.
There is one point that tries to access commit log: offline tools like
sstablescrub tries to delete data from system.sstable_activity after scrubbing
SSTable. This causes access to commit log and since we are trying to disable,
the tool hangs at
[here|https://github.com/apache/cassandra/blob/cassandra-2.1.13/src/java/org/apache/cassandra/db/commitlog/CommitLogSegmentManager.java#L271].
Previously I stated that many offline tools cannot run with
{{Client.setClientMode(true)}}, so reading from SSTableReader tracks sstable
activity even we are ofline.
Probably we should consider rewriting tools so that they never use
ColumnFamilyStore.
> 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)
