Configuring on one server and restarting the other servers is not an option for me since my users are allowed to create their own communities and they would want it available immediately.
Currently I am doing it by having a table that keeps track of node_id/peer_ip and a scheduled proc that runs on each server and updates its site node nsv set by looking at the entries belonging that ip . The entries for each ip gets cleared when the server restarts. But then this is not exactly the best solution because of the latency involved.
I have similar issues with nsv sets being used at many places in the code which donnot get synchronized.
Thanks for the reply.
