Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 5 Oct 2015 18:16:27 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12767307.1421191655000.28367.1444068987712@Atlassian.JIRA>
In-Reply-To: <JIRA.12767307.1421191655000@Atlassian.JIRA>
References: <JIRA.12767307.1421191655000@Atlassian.JIRA>
 <JIRA.12767307.1421191655742@arcas>
Subject: [jira] [Updated] (CASSANDRA-8616) sstable2json may result in commit
 log segments be written
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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