Andrey, In current default configuration affinity is already based on address/port pair, not node ID, and therefore should survive node restarts. You can also provide your own hash ID resolver to customize this (e.g. use some special node attribute): RendezvousAffinityFunction.setHashIdResolver()
setConsistentId() property that will appear in next release only simplifies this process - you will not need to implement the whole resolver if you just want to replace address/port with a different value. Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteConfiguration-setNodeId-usage-clarification-tp818p835.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
