You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ahmed Bashir (JIRA)" <ji...@apache.org> on 2012/10/05 00:53:47 UTC
[jira] [Created] (CASSANDRA-4767) Need some indication of node
repair success or failure
Ahmed Bashir created CASSANDRA-4767:
---------------------------------------
Summary: Need some indication of node repair success or failure
Key: CASSANDRA-4767
URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
Project: Cassandra
Issue Type: Improvement
Affects Versions: 1.1.4
Reporter: Ahmed Bashir
We are currently verifying node repair status via basic log analysis. In order to automatically track the status of periodic node repair jobs, it would be better to have an indicator (through JMX perhaps).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4767) Need some indication of node
repair success or failure
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491602#comment-13491602 ]
Nick Bailey commented on CASSANDRA-4767:
----------------------------------------
Our approach with these jmx type operations in the past has been let the jmx call block until it finishes. That does have some downsides though like checking progress and jmx timeouts.
If we do this we should hopefully make it generic enough to hook all of our long running jmx calls in to.
> Need some indication of node repair success or failure
> ------------------------------------------------------
>
> Key: CASSANDRA-4767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Ahmed Bashir
> Assignee: Yuki Morishita
> Labels: jmx
> Fix For: 1.1.7, 1.2.0
>
>
> We are currently verifying node repair status via basic log analysis. In order to automatically track the status of periodic node repair jobs, it would be better to have an indicator (through JMX perhaps).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4767) Need some indication of node
repair success or failure
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4767:
--------------------------------------
Priority: Minor (was: Major)
Fix Version/s: (was: 1.2.0)
1.2.1
> Need some indication of node repair success or failure
> ------------------------------------------------------
>
> Key: CASSANDRA-4767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Ahmed Bashir
> Assignee: Yuki Morishita
> Priority: Minor
> Labels: jmx
> Fix For: 1.1.7, 1.2.1
>
>
> We are currently verifying node repair status via basic log analysis. In order to automatically track the status of periodic node repair jobs, it would be better to have an indicator (through JMX perhaps).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4767) Need some indication of node
repair success or failure
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491615#comment-13491615 ]
Jonathan Ellis commented on CASSANDRA-4767:
-------------------------------------------
None? of the other ones have the concept of a unique session so that's broadening the scope significantly.
> Need some indication of node repair success or failure
> ------------------------------------------------------
>
> Key: CASSANDRA-4767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Ahmed Bashir
> Assignee: Yuki Morishita
> Labels: jmx
> Fix For: 1.1.7, 1.2.0
>
>
> We are currently verifying node repair status via basic log analysis. In order to automatically track the status of periodic node repair jobs, it would be better to have an indicator (through JMX perhaps).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4767) Need some indication of node
repair success or failure
Posted by "Nick Bailey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491795#comment-13491795 ]
Nick Bailey commented on CASSANDRA-4767:
----------------------------------------
Darn.
> Need some indication of node repair success or failure
> ------------------------------------------------------
>
> Key: CASSANDRA-4767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Ahmed Bashir
> Assignee: Yuki Morishita
> Labels: jmx
> Fix For: 1.1.7, 1.2.0
>
>
> We are currently verifying node repair status via basic log analysis. In order to automatically track the status of periodic node repair jobs, it would be better to have an indicator (through JMX perhaps).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4767) Need some indication of node
repair success or failure
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4767:
--------------------------------------
Component/s: Tools
Affects Version/s: (was: 1.1.4)
Fix Version/s: 1.2.0
1.1.7
Assignee: Yuki Morishita
Labels: jmx (was: )
Yes, JMX is the right place for this.
One possible API: a List of Map<String: String>:
{'Session': session id,
'Initiator': node "coordinating" the repair,
'Status': 'Pending'|'Validating'|'Repairing'|'Success'|'Failed',
'Started': start timestamp,
'Finished': finish timestamp}
If this is unintrusive enough we can try to get it into 1.1.x; otherwise, an early 1.2 release.
/cc [~j.casares]
> Need some indication of node repair success or failure
> ------------------------------------------------------
>
> Key: CASSANDRA-4767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4767
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Ahmed Bashir
> Assignee: Yuki Morishita
> Labels: jmx
> Fix For: 1.1.7, 1.2.0
>
>
> We are currently verifying node repair status via basic log analysis. In order to automatically track the status of periodic node repair jobs, it would be better to have an indicator (through JMX perhaps).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira