Alexey Goncharuk created IGNITE-10495: -----------------------------------------
Summary: Get rid of local node ID in IgniteConfiguration Key: IGNITE-10495 URL: https://issues.apache.org/jira/browse/IGNITE-10495 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk Fix For: 3.0 Partially the ticket is motivated by IGNITE-10484. Currently the local node ID is stored in the instance of local node which sometimes may cause tricky deadlocks. This node ID may be regenerated on clients when the client reconnects to the cluster. On the other hand, we have a deprecated method {{IgniteConfiguration#getNodeId}} which is heavily used in the codebase, which obviously breaks after the client reconnect. I suggest to remove the node ID from the configuration in 3.0 since it is already deprecated, and move the local node ID from the node instance to {{IgniteKernal}} so that we do not need the SPI context to get this ID. -- This message was sent by Atlassian JIRA (v7.6.3#76005)