[
https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305850#comment-14305850
]
Wade Simmons commented on CASSANDRA-8616:
-----------------------------------------
I am seeing what appears to be the same issue in 1.2.16. Using sstable2json is
trying to open the commitlog files for writing:
{noformat}
$ sstable2json <sstable-Data.db>
Exception in thread "COMMIT-LOG-ALLOCATOR" FSWriteError in
/var/lib/cassandra/commitlog/CommitLog-2-1423079861481.log
]
at
org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:132)
at
org.apache.cassandra.db.commitlog.CommitLogSegment.freshSegment(CommitLogSegment.java:81)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator.createFreshSegment(CommitLogAllocator.java:251)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator.access$500(CommitLogAllocator.java:49)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(CommitLogAllocator.java:105)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
at java.lang.Thread.run(Thread.java:695)
Caused by: java.io.FileNotFoundException:
/var/lib/cassandra/commitlog/CommitLog-2-1423079861481.log (Permission denied)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:216)
at
org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:116)
... 6 more
{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: Yuki Morishita
> Fix For: 2.1.3, 2.0.13
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
