[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493908#comment-15493908
]
Tyler Hobbs commented on CASSANDRA-8616:
----------------------------------------
The patches seem fine to me, but there are some problems in the tests. It
seems like the 2.2 testall failures around SSTableRewriter could be related to
this, since they don't show up in normal 2.2 test failures. The 3.0 and 3.3
dtests are erroring out when trying to copy test results at the end, but if I
remember correctly, this can be caused by some tests not terminating, so we
should investigate that. The trunk RemoveTest failure in testall could also be
related to this patch.
> 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.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)
