cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wade Simmons (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8616) sstable2json may result in commit log segments be written
Date Wed, 04 Feb 2015 20:01:35 GMT


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:

$ 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>(
	at org.apache.cassandra.db.commitlog.CommitLogSegment.freshSegment(
	at org.apache.cassandra.db.commitlog.CommitLogAllocator.createFreshSegment(
	at org.apache.cassandra.db.commitlog.CommitLogAllocator.access$500(
	at org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(
Caused by: /var/lib/cassandra/commitlog/CommitLog-2-1423079861481.log
(Permission denied)
	at Method)
	at org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(
	... 6 more

> sstable2json may result in commit log segments be written
> ---------------------------------------------------------
>                 Key: CASSANDRA-8616
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message