[sr-dev] [kamailio/kamailio] sequence breaking DMQ bus (#1349)

Julien Chavanton notifications at github.com
Sun Dec 3 02:07:20 CET 2017


I also tried the ring strategy but, I did not like the fact that if you loose one server the ring may get broken. 

Maybe this is still better in the end but when you have a lot of server it is more likely that one server may be removed from service.

This is why I am testing with a "master" node
Not sure what is you opinion 

Example of broken state with a ring config and 4 servers: 
```
/etc/init.d/kamailio_second stop
/etc/init.d/kamailio_third stop
/etc/init.d/kamailio_second start
```

You end up with 
```
show dmq bus: first	
host: 127.0.0.103 	status: 8 	last_notification: 0 	local: 0 	
host: 127.0.0.104 	status: 2 	last_notification: 0 	local: 0 	
host: 127.0.0.102 	status: 8 	last_notification: 0 	local: 0 	
host: 127.0.0.101 	status: 2 	last_notification: 0 	local: 1 
show dmq bus: second	
host: 127.0.0.103 	status: 2 	last_notification: 0 	local: 0 	
host: 127.0.0.102 	status: 2 	last_notification: 0 	local: 1 
show dmq bus: third          not running !
show dmq bus: fourth	
host: 127.0.0.102 	status: 8 	last_notification: 0 	local: 0 	
host: 127.0.0.103 	status: 8 	last_notification: 0 	local: 0 	
host: 127.0.0.101 	status: 2 	last_notification: 0 	local: 0 	
host: 127.0.0.104 	status: 2 	last_notification: 0 	local: 1 
```


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1349#issuecomment-348732404
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20171203/7d08a56e/attachment.html>


More information about the sr-dev mailing list