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

Posted to commits@cassandra.apache.org by "Russ Hatch (JIRA)" <ji...@apache.org> on 2015/01/24 00:20:35 UTC

[jira] [Reopened] (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:all-tabpanel ]

Russ Hatch reopened CASSANDRA-8616:
-----------------------------------

Seems to be working fine in 2.0 latest, but latest 2.1 (c468c8b436) is still writing commitlog files when sstable2json is called.

Similar to before, this happens whether the db file argument is valid or not, and each time 1 new commitlog file is written.

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