Thanks for the reply!
> Not really:
>
> - range scans do not perform read repair
Ok I obviously overlooked that RangeSliceResponseResolver does not repair rows
on nodes that never saw a write for a given key at all. But that's not a big
problem for us since we are mainly interested in fixing m
On Mon, Mar 7, 2011 at 11:18 AM, Daniel Doubleday
wrote:
> Since we already have a very simple hadoopish framework in place which allows
> us to do token range walks with multiple workers and restart at a given
> position in case of failure I created a simple worker that would read
> everything
Hi all
we're still on 0.6 and are facing problems with repairs.
I.e. a repair for one CF takes around 60h and we have to do that twice (RF=3, 5
nodes). During that time the cluster is under pretty heavy IO load. It kinda
works but during peek times we see lots of dropped messages (including wr
