On 17 December 2013 19:47, Robert Coli wrote:
> I would comment to that effect on CASSANDRA-6210, were I you.
Will do.
> Are you using vnodes? Have you tried a rolling restart of all nodes?
Yes, we're using vnodes, and all nodes have been restarted since this
problem started happening.
--
Rus
On Tue, Dec 17, 2013 at 4:32 AM, Russ Garrett wrote:
> This seems to be the same error as CASSANDRA-6210, however there are
> no nodes bootstrapping (I haven't added any nodes since starting the
> cluster up).
>
I would comment to that effect on CASSANDRA-6210, were I you.
Are you using vnodes?
Using Cassandra 2.0.3, I'm seeing repairs hanging on all nodes on our
cluster. On the node running the repair, the error is:
Caused by: org.apache.cassandra.exceptions.RepairException: [repair
#8d77b2a0-670b-11e3-949c-6176e8469a51 on OpsCenter/rollups300,
(251968055115794,2549561992225510945]]
