Strange, I've never seen consistent IDs collisions before. Are you using Ignite persistence and what's your version? If you scroll to the end of this paragraph, you'll find an explanation on how the IDs are generated: https://apacheignite.readme.io/docs/distributed-persistent-store#section-usage
-- Denis On Thu, Aug 30, 2018 at 9:10 PM eugene miretsky <[email protected]> wrote: > Hello, > > Is it possible to set a nodeId when restarting a node? How is the id > generated? > > Sometimes after the cluster crashes, when I restart a node I get the > following error: Caused by: class > org.apache.ignite.spi.IgniteSpiException: Failed to add node to topology > because it has the same hash code for partitioned affinity as one of > existing nodes [cacheName=SQL_PUBLIC_GAL3EC2, > existingNodeId=598e3ead-99b8-4c49-b7df-04d578dcbf5f] > > It looks like the node is trying to start with another nodeId, and cannot > because it's old nodeId owns the same partitions. > > Cheers, > Eugene >
