[sr-dev] [tracker] Task opened: dispatcher doesn't loadbalance correctly if one target is offline (Attachment added)

sip-router bugtracker at sip-router.org
Mon Aug 18 14:08:11 CEST 2014


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Sebastian Damm (sdamm) 

Attached to Project - sip-router
Summary - dispatcher doesn't loadbalance correctly if one target is offline
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To - 
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - We're running a dispatcher setup where a loadbalancer sends traffic to a couple of proxy servers. Now if one proxy server is offline, the users from this proxy server are sent to exactly ONE other proxy server. This way, the customers still get their service, but one server has more load than the others. What I would expect is, that the dispatcher module recalculates the target and sends it equally distributed to the remaining servers.

I have setup a test environment, took the sample kamailio.cfg and edited it as needed. Had one load balancer and four registrar servers. Then I took sipp and sent 1000 REGISTER requests to the loadbalancer. I have attached a screenshot of kamctl moni of all registrars to see how they were distributed. As you can see in the first screenshot, it is equally distributed as expected. 
Then I disabled proxy4. I restarted the other registrars, then sent the same 1000 requests to the load balancer. The second screenshot shows how they were distributed. As you can see, proxy3 got all the registrations from proxy4, while proxy1 and proxy2 remained at the exact same number as before.

I have attached my sample configs as well.

One or more files have been attached.

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=460

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the sr-dev mailing list