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

Posted to commits@cassandra.apache.org by "Philip S Doctor (JIRA)" <ji...@apache.org> on 2015/02/04 00:22:34 UTC

[jira] [Created] (CASSANDRA-8734) Expose commit log archive status

Philip S Doctor created CASSANDRA-8734:
------------------------------------------

             Summary: Expose commit log archive status
                 Key: CASSANDRA-8734
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8734
             Project: Cassandra
          Issue Type: New Feature
          Components: Config
            Reporter: Philip S Doctor


The operational procedure to modify commit log archiving is to edit commitlog_archiving.properties and then perform a restart.  However this has troublesome edge cases:

1) It is possible for people to modify commitlog_archiving.properties but then not perform a restart

2) It is possible for people to modify commitlog_archiving.properties 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 commitlog_archiving.properties 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
(v6.3.4#6332)