On Wed, Apr 16, 2014 at 3:17 PM, Andrew Cooper <andrew.coo...@nisc.coop>wrote:
> We are running cassandra 1.2.5. I have checked through the change logs up > to 1.2.16 and do not see any indications of this being a known (and fixed) > issue. > Repair has been re-written in 2.0, because it was broken; that's why you don't see notes about it being patch fixed in the 1.2 series. https://issues.apache.org/jira/browse/CASSANDRA-5286 As to the background here, while the tone of the ticket filer in this JIRA is inappropriate for participation in an open source community, this ticket briefly (and IMO accurately) summarizes how repair was broken and therefore why it was re-written in 2.0 : https://issues.apache.org/jira/browse/CASSANDRA-5396 There are some minor streaming fixes in the 1.2 line which may help your case, but in any case 1.2.5 has other serious issues; if I were you I would start by upgrading to 1.2.16. The only way we can clear this is to restart cassandra on the node > Your input as an operator is welcome here : https://issues.apache.org/jira/browse/CASSANDRA-3486 I would appreciate any feedback or advice on this. thanks > Are you sure you actually want/need to run repair as frequently as you currently are? Reducing the frequency won't make it work any better, but it will reduce the number of times you have to babysit its failure. https://issues.apache.org/jira/browse/CASSANDRA-5850 =Rob
