Just wondering - why do you have to trigger the repairs? Is that necessary in Cassandra?
(Sorry for the off topic question) On Thu, Mar 19, 2015 at 10:30 PM, Ian Rose <ianr...@fullstory.com> wrote: > Howdy - > > I'd like to (a) monitor how long my repairs are taking, and (b) know when > a repair is finished so that I can take some kind of followup action. > What's the best way to tackle either or both of these? > > Some potentially relevant details: > > - running community apache cassandra (not DSE) > - version 2.0.13 > - we currently trigger repairs via an external timer that > calls forceRepairAsync on the StorageService mbean via JMX > > Thanks! > - Ian > >
