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

2015-04-03 Thread Tyler Hobbs (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tyler Hobbs updated CASSANDRA-8734:
---
Fix Version/s: 2.0.15

 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
Assignee: Chris Lohfink
Priority: Minor
 Fix For: 2.0.15, 2.1.5

 Attachments: 8734-cassandra-2.0.txt, 8734-cassandra-2.1.txt


 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)


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

2015-03-10 Thread Chris Lohfink (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Lohfink updated CASSANDRA-8734:
-
Attachment: 8734-cassandra-2.0.txt

 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
Assignee: Chris Lohfink
Priority: Minor
 Fix For: 2.1.4

 Attachments: 8734-cassandra-2.0.txt, 8734-cassandra-2.1.txt


 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)


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

2015-03-10 Thread Chris Lohfink (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Lohfink updated CASSANDRA-8734:
-
Attachment: (was: 8734-cassandra-2.0.txt)

 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
Assignee: Chris Lohfink
Priority: Minor
 Fix For: 2.1.4

 Attachments: 8734-cassandra-2.0.txt, 8734-cassandra-2.1.txt


 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)


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

2015-03-10 Thread Chris Lohfink (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Lohfink updated CASSANDRA-8734:
-
Attachment: 8734-cassandra-2.0.txt

 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
Assignee: Chris Lohfink
Priority: Minor
 Fix For: 2.1.4

 Attachments: 8734-cassandra-2.0.txt, 8734-cassandra-2.1.txt


 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)


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

2015-02-17 Thread Joshua McKenzie (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua McKenzie updated CASSANDRA-8734:
---
Fix Version/s: 2.1.4

 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
Assignee: Chris Lohfink
 Fix For: 2.1.4

 Attachments: 8734-cassandra-2.1.txt


 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)


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

2015-02-17 Thread Joshua McKenzie (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua McKenzie updated CASSANDRA-8734:
---
Priority: Minor  (was: Major)

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


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

2015-02-04 Thread Joshua McKenzie (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua McKenzie updated CASSANDRA-8734:
---
Reviewer: Joshua McKenzie

 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
Assignee: Chris Lohfink
 Attachments: 8734-cassandra-2.1.txt


 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)


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

2015-02-03 Thread Chris Lohfink (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Lohfink updated CASSANDRA-8734:
-
Attachment: 8734-cassandra-2.1.txt

 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
 Attachments: 8734-cassandra-2.1.txt


 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)