I think I'd rather have it be an option to repair (--primary-range-only) than a new command.
-1 on doing anything more with clustertool than putting it out of its misery (
Fair enough, v2 does both of those thing.
How does "primary range repair" work with NTS, where ranges are unique to each DC?
Not sure what you mean by "ranges are unique to each DC". Even with NTS, the
primary ranges are still computed over the one full ring (that rule them all).
So picking the primary range still has the property we are interested in here,
that is "if you repair the primary range of all the node of the full
cluster, then you will have repaired the full ring without doing any work
Now it is true that since with NTS you compute your token assignment
separately in each DC you may end up with some node having tiny primary range
(for instance if you have the same number of nodes in each DC and only offset
the tokens by 1 across DC). In which case the repair on those nodes will be
very quick. But I don't think this is a problem in any way (every host will
still do roughly the same amount of work overall).
However, maybe what you meant is that "repair is not optimized for multi-DC
settings". Which is a very good remark but is really a whole new problem. I'll
open a ticket for that.