[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156706#comment-15156706
]
Sylvain Lebresne commented on CASSANDRA-8616:
---------------------------------------------
bq. That is sounding like a better option to me, too.
Right, but I'll also note that some people seems to have run into this with
pretty nasty consequences. So I'm all for a clean solution here, but unless
"rewriting tools so that they never use ColumnFamilyStore" is a lot more
trivial than it sounds to me, we might need a quick-n-dirty fix that is
suitable for 2.1 here. And what I mean by that is that we might want to add
some "offline" mode (different from "client mode" since you say we can't use
that) that skips what shouldn't be done by offline tools (like deleting data
from {{system.sstable_activity}}, which sounds to me like something we probably
can just skip when doing an offline scrub).
> 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)
