cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <>
Subject Re: Unable to repair a node
Date Tue, 16 Aug 2011 20:56:18 GMT
On Tue, Aug 16, 2011 at 3:48 PM, Philippe <> wrote:
> I have been able to repair some small column families by issuing a repair
> [KS] [CF]. When testing on the ring with no writes at all, it still takes
> about 2 repairs to get "consistent" logs for all AES requests.

I think I linked these in another of your threads, but this is

> Launching a repair one the smallest CF of the biggest KS has triggered a
> flurry of compactions and streams. Some of those streams are for other CF in
> that keyspace !?

and this is

> What is surprising to me (bug?) is that netstats shows me streams going from
> node A to node B at 0% progress. But netstats on node B doesn't show me any
> streams coming in.

If you are on < 0.8.4 this is probably  Otherwise it
may be a different bug we don't have a ticket for yet.

Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support

View raw message