Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of tholzer@wetafx.co.nz designates
 110.232.144.26 as permitted sender)
Message-ID: <4E3B1644.4000001@wetafx.co.nz>
Date: Fri, 05 Aug 2011 09:59:32 +1200
From: Teijo Holzer <tholzer@wetafx.co.nz>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:5.0) Gecko/20110705 Thunderbird/5.0
MIME-Version: 1.0
To: user@cassandra.apache.org
CC: Bart Swedrowski <bart@timedout.org>
Subject: Re: Last manual repair time
References: 
 <CAFBzO+E+-WhaQBxSHqUTdvpp2CcHG3Q8BFXEL9dSQUFDjNV6_Q@mail.gmail.com>
In-Reply-To: 
 <CAFBzO+E+-WhaQBxSHqUTdvpp2CcHG3Q8BFXEL9dSQUFDjNV6_Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

That's simple, set your log level to INFO in log4j-server.properties and then 
do the following:

Start of every repair:
grep 'Waiting for repair requests:' system.log

End of every  repair:
grep 'No neighbors to repair with' system.log

If you perform individual repairs for each keyspace/column family you might 
need to change the expression in the grep.

These definitely catch all the manual repairs, I don't know if any read repairs 
would show up here as well.

Cheers,

	T.

On 04/08/11 21:44, Bart Swedrowski wrote:
> Hello,
>
> I was going through documentation, however couldn't find anything about whether
> Cassandra stores somewhere information about when manual repair occurred last
> time?  I could script it out but before I do this would like to make sure it's
> not being kept somewhere already.
>
> Obviously this information would be quite useful for monitoring purposes (eg.
> Nagios).
>
> Kind regards