I know this could have been discussed in several posts. But I couldn't find a solution yet. This happens in few cases[not always]. When a data node moves out of the network and comes back, it is not getting registered to cluster automatically. I end up restarting the routing node process to identify the data node
Is it required to restart the routing/coordinator process when data node disconnects from network and comes back?
Or is there any setting I can change to increase the number of checks from cluster for new nodes when a node goes out of network?