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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/10/05 20:16:27 UTC

[jira] [Updated] (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 ]

Jonathan Ellis updated CASSANDRA-8616:
--------------------------------------
    Reproduced In: 2.1.3, 2.0.10  (was: 2.0.10, 2.1.3)
         Priority: Critical  (was: Major)

Bumping to critical since this can prevent startup when sstable2json creates a new segment as root. 

> 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
>            Priority: Critical
>             Fix For: 2.1.x
>
>         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)