Possibly.  I don't fully understand the behavior, but I think it is like this (this should be testable):

scenario 1. thread is not sleeping.  thread.interrupt(), thread.sleep(), BANG-InterruptedException thrown.
scenario 2. thread is already sleeping. thread.interrupt(), BANG-InterruptedException thrown.

The behavior in LocatorFetchRunnable would be problematic if the exception were never not thrown or LOCATOR_WAIT_FOR_ALL_SECS were large enough to give the perception that slots were not being scheduled.

tl;dr: I think we're safe. If we've ever seen an instance where it looks like a `LocatorFetchRunnable` never finished, this would be a good place to start debugging.