[CASSANDRA-8616] sstable tools may result in commit log segments be written

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.9, 3.0.11, 3.10
• Component/s: Legacy/Tools
• Severity: Normal
• Assignee: Yuki Morishita
• Reporter: Tom Hobbs

Authors

Yuki Morishita

Reviewers

Tom Hobbs

• Tester: Russ Hatch
• Created: 13/Jan/15 23:27
• Updated: 16/Apr/19 09:31
• Resolved: 14/Dec/16 00:46

Description

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.

Issue Links

• incorporates: CASSANDRA-12534 sstableverify tries to access commitlog directory and fails when running from a non-root/non-cassandra user
• is related to: CASSANDRA-13605 threads created during classload-static sections open commitlog handles
• relates to: CASSANDRA-9054 Let DatabaseDescriptor not implicitly startup services