cassandra-commits mailing list archives

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


Yuki Morishita commented on CASSANDRA-8616:

I took another approach in the new patches.
Since the source of accessing commit log is {{Memtable}}, I changed {{Tracker}} to have {{Memtable}}
optional when only on online. (This change may also be useful for future offline tools change.)

There are several places that try to update system tables (sstable_activity, secondary index,
compaction) so I manually had to disabled them by checking {{DatabaseDescriptor.isDaemonInitialized}}
(in trunk, added similar method to 2.2 and 3.0), or offline tool can hang.


(test is still running for some)

> 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.1.x, 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