Hi guys. It seems that there were 2 streams hanging to one node, restarting this targeted node seems to have solved my issue, repairs are now running. Waiting to see if it completes.
"Try repairing only one CF at a time, starting with the smallest ones and/or the ones whose data you care about the most?" Thanks Robert, I believe this is a good idea but I was doing it already. "If you are really overprovisioned and on real hardware and network and SSD, it might work sometimes." I am on AWS and was on m1.small to m1.xlarge from Cassandra 0.8 to 1.2.18, that's the first time a repair hangs for me. At least it is the first time I notices it. Maybe were I lucky somehow. Anyway, thanks for helping once again. Alain 2014-10-20 19:33 GMT+02:00 Robert Coli <rc...@eventbrite.com>: > On Mon, Oct 20, 2014 at 5:45 AM, Alain RODRIGUEZ <arodr...@gmail.com> > wrote: > >> I now that 2.1 fixes this all. We are going to migrate to C* 2.0 soon >> (asap) and then to 2.1, but we first need to run some tests, which will >> take us some time. Is repair officially broken on 1.2.18 ? Is there any >> known workaround or solutions to get data repaired on this version ? >> > > One more thing : > > Try repairing only one CF at a time, starting with the smallest ones > and/or the ones whose data you care about the most? > > =Rob > >
