You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Coverston (JIRA)" <ji...@apache.org> on 2011/09/14 20:07:08 UTC
[jira] [Created] (CASSANDRA-3207) Log message at INFO when a global
or keyspace level repair operation completes
Log message at INFO when a global or keyspace level repair operation completes
------------------------------------------------------------------------------
Key: CASSANDRA-3207
URL: https://issues.apache.org/jira/browse/CASSANDRA-3207
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8.5
Reporter: Benjamin Coverston
If JMX times out it's difficult to tell when repair completes.Right now we log at DEBUG for each column family but we need a way to tell when the repair operation completes as a whole.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3207) Log message at INFO when a global
or keyspace level repair operation completes
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-3207:
----------------------------------------
Attachment: 3207.patch
Attached patch adds two new log messages:
* at the completion of a repair session. This part is already in 1.0.0 but not in 0.8.
* at the beginning and total completion of a repair "command". A command being basically a 'nodetool repair' call, that usually consist of multiple session (one by token range).
> Log message at INFO when a global or keyspace level repair operation completes
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3207
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3207
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.5
> Reporter: Benjamin Coverston
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: logging, repair
> Fix For: 0.8.7
>
> Attachments: 3207.patch
>
>
> If JMX times out it's difficult to tell when repair completes.Right now we log at DEBUG for each column family but we need a way to tell when the repair operation completes as a whole.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3207) Log message at INFO when a global
or keyspace level repair operation completes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3207:
--------------------------------------
Priority: Minor (was: Major)
Fix Version/s: 0.8.6
Assignee: Sylvain Lebresne
> Log message at INFO when a global or keyspace level repair operation completes
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3207
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3207
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.5
> Reporter: Benjamin Coverston
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: logging, repair
> Fix For: 0.8.6
>
>
> If JMX times out it's difficult to tell when repair completes.Right now we log at DEBUG for each column family but we need a way to tell when the repair operation completes as a whole.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3207) Log message at INFO when a
global or keyspace level repair operation completes
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107807#comment-13107807 ]
Hudson commented on CASSANDRA-3207:
-----------------------------------
Integrated in Cassandra-0.8 #335 (See [https://builds.apache.org/job/Cassandra-0.8/335/])
Log message at INFO when a global or keyspace level repair operation completes
patch by slebresne; reviewed by jbellis for CASSANDRA-3207
slebresne : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1172591
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/AntiEntropyService.java
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/StorageService.java
> Log message at INFO when a global or keyspace level repair operation completes
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3207
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3207
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.5
> Reporter: Benjamin Coverston
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: logging, repair
> Fix For: 0.8.7
>
> Attachments: 3207.patch
>
>
> If JMX times out it's difficult to tell when repair completes.Right now we log at DEBUG for each column family but we need a way to tell when the repair operation completes as a whole.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3207) Log message at INFO when a
global or keyspace level repair operation completes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106723#comment-13106723 ]
Jonathan Ellis commented on CASSANDRA-3207:
-------------------------------------------
+1
> Log message at INFO when a global or keyspace level repair operation completes
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3207
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3207
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.5
> Reporter: Benjamin Coverston
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: logging, repair
> Fix For: 0.8.7
>
> Attachments: 3207.patch
>
>
> If JMX times out it's difficult to tell when repair completes.Right now we log at DEBUG for each column family but we need a way to tell when the repair operation completes as a whole.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3207) Log message at INFO when a global
or keyspace level repair operation completes
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-3207:
----------------------------------------
Fix Version/s: (was: 0.8.6)
0.8.7
> Log message at INFO when a global or keyspace level repair operation completes
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3207
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3207
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.5
> Reporter: Benjamin Coverston
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: logging, repair
> Fix For: 0.8.7
>
>
> If JMX times out it's difficult to tell when repair completes.Right now we log at DEBUG for each column family but we need a way to tell when the repair operation completes as a whole.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira