Fix Version/s: 2.0.9
From what I can tell the calculation (using the -pr option) and validation of tokens for repairing ranges is broken. Or at least should be improved. Using an example with ccm:
Note that repairing both nodes in dc1, leaves very small ranges unrepaired. For example (-10,0]. Repairing the 'primary range' in dc2 will repair those small ranges. Maybe that is the behavior we want but it seems counterintuitive.
The behavior when manually trying to repair the full range of 127.0.0.01 definitely needs improvement though.
- The actual output of the repair command doesn't really indicate that there was an issue. Although the command does return with a non zero exit status.
- The error here is invisible if you are using the synchronous jmx repair api. It will appear as though the repair completed successfully.
- Personally, I believe that should be a valid repair command. For the system_traces keyspace, 127.0.0.1 is responsible for this range (and I would argue the 'primary range' of the node).