cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8734) Expose commit log archive status
Date Tue, 17 Feb 2015 17:54:12 GMT


Joshua McKenzie commented on CASSANDRA-8734:

It's a bean modification w/read-only and a touch of scope change - I'm comfortable adding
this to 2.0.

Code LGTM - could you rebase to 2.0 [~cnlwsu]?  I'll get it committed as soon as we have a
2.0 version and merge it up.

> Expose commit log archive status
> --------------------------------
>                 Key: CASSANDRA-8734
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Config
>            Reporter: Philip S Doctor
>            Assignee: Chris Lohfink
>            Priority: Minor
>             Fix For: 2.1.4
>         Attachments: 8734-cassandra-2.1.txt
> The operational procedure to modify commit log archiving is to edit
and then perform a restart.  However this has troublesome edge cases:
> 1) It is possible for people to modify but then not perform
a restart
> 2) It is possible for people to modify only on some nodes
> 3) It is possible for people to have modified file + restart but then later add more
nodes without correct modifications.
> Because of these reasons, it is operationally useful to be able to audit the commit log
archive state of a node.  Simply parsing is insufficient due
to #1.  
> I would suggest exposing either via some system table or JMX would be useful.

This message was sent by Atlassian JIRA

View raw message