[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276270#comment-14276270
]
Russ Hatch commented on CASSANDRA-8616:
---------------------------------------
This indeed seems to be the case with 2.0.10, and it's even happening if you
invoke sstable2json incorrectly.
To repro I ran cassandra-stress, and killed the cassandra process while stress
was still running. Then I ran sstable2json (with a bad sstable filename, and
with a valid one) and new commitlog files are created.
{noformat}
root@ce986ee973c1:/cassandra# ls -ltr /var/lib/cassandra/commitlog | wc -l
11
root@ce986ee973c1:/cassandra# bin/sstable2json thisfiledoesntexist.db >
/dev/null
Exception in thread "main" java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
at
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:235)
at
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:204)
at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:452)
^C
root@ce986ee973c1:/cassandra# ls -ltr /var/lib/cassandra/commitlog | wc -l
12
{noformat}
> sstable2json 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: Russ Hatch
> Fix For: 2.0.13
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
