Romain, I had another repair that seems to just hang last night. When I did 'nodetool tpstats' on nodes, I see the following in the node where I initiated the repair: AntiEntropySessions 1 1 On all other nodes, I see: AntiEntropySessions 0 0 When I check the log for pattern "session completed successfully" in system.log, I see the last finished range occurred in 14 hours ago. So I think it is safe to say that the repair has hanged somehow. In order to start another repair, do we need to 'kill' this repair. If so, how do we do that?
Thanks. George. On Thu, Sep 22, 2016 at 6:23 AM, Romain Hardouin <romainh...@yahoo.fr> wrote: > I meant that pending (and active) AntiEntropySessions are a simple way to > check if a repair is still running on a cluster. Also have a look at > Cassandra reaper: > - https://github.com/spotify/cassandra-reaper > > - https://github.com/spodkowinski/cassandra-reaper-ui > > Best, > Romain > > > > Le Mercredi 21 septembre 2016 22h32, "Li, Guangxing" < > guangxing...@pearson.com> a écrit : > > Romain, > > I started running a new repair. If I see such behavior again, I will try > what you mentioned. > > Thanks. >
