cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-8616) sstable tools may result in commit log segments be written
Date Tue, 13 Sep 2016 17:20:20 GMT


Yuki Morishita updated CASSANDRA-8616:
    Reproduced In: 2.1.3, 2.0.10  (was: 2.0.10, 2.1.3)
           Status: Open  (was: Patch Available)

Unit test failures in trunk revealed that I need to patch where we query Memtable and SSTables
since current code assumes there is at least one iterator there. Will update the patch.

> sstable tools 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.2.x, 3.0.x, 3.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
> sstablescrub, sstableverify, and other sstable tools have the same issue.

This message was sent by Atlassian JIRA

View raw message