cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Sargisson <>
Subject Re: Nodetool repair, exit code/status?
Date Tue, 09 Oct 2012 16:46:03 GMT
This is a problem for us as well.
Our current planned approach is to parse the logs for repair errors.
Having nodetool repair return an exit code for some of this failures 
would be *very* useful.


On 12-10-08 06:49 PM, David Daeschler wrote:
> Hello.
> In the process of trying to streamline and provide better reporting
> for various data storage systems, I've realized that although we're
> verifying that nodetool repair runs, we're not verifying that it is
> successful.
> I found a bug relating to the exit code for nodetool repair, where, in
> some situations, there is no way to verify the repair has completed
> successfully:
> Is this still a problem? What is the best way to monitor the final
> status of the repair command to make sure all is well?
> Thank you ahead of time for any info.
> - David


Edward Sargisson

senior java developer
Global Relay <>

New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore 

Global Relay Archive supports email, instant messaging, BlackBerry, 
Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, 
Facebook and more.

Ask about *Global Relay Message* 
<>*--- *The Future of 
Collaboration in the Financial Services World

*All email sent to or from this address will be retained by Global 
Relay's email archiving system. This message is intended only for the 
use of the individual or entity to which it is addressed, and may 
contain information that is privileged, confidential, and exempt from 
disclosure under applicable law.  Global Relay will not be liable for 
any compliance or technical information provided herein. All trademarks 
are the property of their respective owners.

View raw message