Alright, so I don't think it's findSuccessor's fault

It can handle threads doing simultanious lookups
Definately not findSuccessor's fault.