You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/01/14 00:32:34 UTC

[jira] [Commented] (CASSANDRA-8616) sstable2json may result in commit log segments be written

    [ https://issues.apache.org/jira/browse/CASSANDRA-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276189#comment-14276189 ] 

Tyler Hobbs commented on CASSANDRA-8616:
----------------------------------------

[~philipthompson] can you try to reproduce this? It may be helpful to run stress for a while, then shut down the node, then run sstable2json on one of the stress tables.

> 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
>             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)