Hi, > Any ideas on how we can end up having consistent IDs conflict on restarts? Well, I see only one reason that can lead to this behavior. This is the case when a new node is trying to join the cluster with a `consistentId` which is already in use, i.e. there is a node with the same `consistentId` (to be more precise, hash codes of consitentIds are the same). Perhaps, someone started a node locally, that joined the cluster and has the same consistentId.
Thanks, S. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
