Thank you for the reply Aaron. Unfortunately, I could not seem to find any
additional info in the logs. However, upgrading from 2.0.2 to 2.0.3 seems to
have done the trick!
Best regards,
-David Laube
On Dec 11, 2013, at 6:51 PM, Aaron Morton wrote:
>> [2013-12-08 11:04:02,047] Repair session
Hi Michael,
Upgrading from 2.0.2 to 2.0.3 seems to have done the trick! Thank you for the
recommendation!
Best regards,
-David Laube
On Dec 9, 2013, at 3:57 PM, "Laing, Michael" wrote:
> My experience is that you must upgrade to 2.0.3 ASAP to fix this.
>
> Michael
>
>
> On Mon, Dec 9, 2013
> [2013-12-08 11:04:02,047] Repair session ff16c510-5ff7-11e3-97c0-5973cc397f8f
> for range (1246984843639507027,1266616572749926276] failed with error
> org.apache.cassandra.exceptions.RepairException: [repair
> #ff16c510-5ff7-11e3-97c0-5973cc397f8f on keyspace_name/col_family1,
> (12469848436
My experience is that you must upgrade to 2.0.3 ASAP to fix this.
Michael
On Mon, Dec 9, 2013 at 6:39 PM, David Laube wrote:
> Hi All,
>
> We are running Cassandra 2.0.2 and have recently stumbled upon an issue
> with nodetool repair. Upon running nodetool repair on each of the 5 nodes
> in th
Hi All,
We are running Cassandra 2.0.2 and have recently stumbled upon an issue with
nodetool repair. Upon running nodetool repair on each of the 5 nodes in the
ring (one at a time) we observe the following exceptions returned to standard
out;
[2013-12-08 11:04:02,047] Repair session ff16c510
