On Mon, Apr 13, 2015 at 11:43 PM, Jeff Ferland <[email protected]> wrote:
> Just read the source and well… yup. I’m guessing now that the options are > indeed only rolling repair on each node (with -pr stopping the duplicate > work) or -st -9223372036854775808 -et 9223372036854775807 to actually cover > all ranges. I didn’t walk through to test that, though. > Technically speaking, in the non-vnode world, you can just run a non-pr repair on certain nodes and repair 100% of the cluster. A B C D E F G H I N=8 RF=3 Without -pr, if you repair C (repairs A,B,D,E) and G (repairs E,F,H,I)... you're done. Vnodes makes this sort of thing too complex to bother with, with the chance that all physical nodes share at least one range with other nodes being quite high. > Glad 3.0 is getting a little bit of love on improving repairs and > communications / logging about them. > +1 =Rob
