Hi Enrico, As you suggested, I tried adding removing a node and adding a new node, in the hope that the config will be updated somehow. But, it did not help. The new node joined the cluster and synced the data and was serving clients the correct data. But, when it assumed leader role, the entire cluster would just go unresponsive. And once leader role moved elsewhere, the cluster would respond. This kinda looks like a bug to me. Could you please check.
And then at last, I did `reconfigEnabled=true` across the cluster. And then used `reconfig` functionality to remove the old/stale node and then added back the new node. Had to restart the nodes couple of times for this to take effect. And this time when the new node assumed leader role, the cluster was responsive and no issues were observed. So, this definitely looks like a bug in some corner which is hard-coded/told look only for dyanmicConfig? Thanks again for your help, much appreciated. Regards, Rajkiran -- Sent from: http://zookeeper-user.578899.n2.nabble.com/
