Hi, Did you restart OpenSIPS process on both node1, and 2 simultaneously ? The way I look at this is one of the two nodes kept the 3rd one in the memory and restarting both nodes one at a time resulted in both sharing their node structure and hence node3 stayed visible. I think possible way to remove a node gracefully would be to disable the node via the MI command and then remove from DB. I will try doing this on my test setup as well.
Regards, Sammy On Fri, Dec 28, 2018 at 6:40 AM Sasmita Panda <[email protected]> wrote: > Hi All, > > I have a cluster of 2 nodes . Both in working condition . Then I added > another node in the same cluster which is down . > > I restarted the opensips process , so it starts pinging the new node to > check its status . As the new node is down , other nodes in the cluster > wont get any reply for the ping . Then I remove the 3rd node from the > cluster table and restart the opensips process . > > Now what I am getting in logs is , still the 2 working node in the cluster > try to ping the 3rd node which is not in the DB . > > Is this an issue on the cluster module or I am doing something wrong ?? > Please help me . > *Thanks & Regards* > *Sasmita Panda* > *Senior Network Testing and Software Engineer* > *3CLogic , ph:07827611765* > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
