12 Aug
2019
12 Aug
'19
9:23 p.m.
Hello,
I pushed a patch that should fix it -- the inactive destinations were
not skipped when pointing to next to be used record, so one active
gateway was used for as many times as many inactive gateways were before
it in that group list.
Let me know if works fine now, patch is in master and 5.2 branches.
Cheers,
Daniel
On 12.08.19 17:28, Alex Balashov wrote:
Hi Daniel,
Haven’t checked that, no. But all the external system does is issue RPC commands
(`dispatcher.set_state`) maybe a few times a day. It’s nothing volatile or overly
Byzantine.
—
Sent from mobile, with due apologies for brevity and errors.
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
On Aug 12, 2019, at 11:24 AM, Daniel-Constantin
Mierla <miconda(a)gmail.com> wrote:
Hello,
could you observe similar behavior on other dispatchers that don't use
an external system tomanage activation and deactivation of the gateways?
Or you haven't checked such one so far?
Cheers,
Daniel
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users On 12.08.19 15:23, Alex Balashov wrote:
Hi,
I've got a proxy that does very basic round-robin distribution of calls
to an elastic pool of servers, defined in a simple SQLite database with
equal priorities. Nothing too complicated, just a vanilla
`ds_select_domain("1", "4")`.
The only complication is that seldom are most of the gateways enabled.
Probing stuff was turned on, but didn't do quite what was desired, so it
was replaced with a system that manages activation and deactivation of
the gateways externally. Nevertheless, these are the left-over probing
settings:
modparam("dispatcher", "ds_ping_method", "OPTIONS")
modparam("dispatcher", "ds_ping_from",
"sip:pinger@domain")
modparam("dispatcher", "ds_ping_interval", 15)
modparam("dispatcher", "ds_probing_threshold", 256)
modparam("dispatcher", "ds_inactive_threshold", 1)
modparam("dispatcher", "ds_probing_mode", 0)
After an upgrade from 5.1 to 5.2.3 (009f62), the round-robin has become
extremely "sticky" and tendentious. That is to say, it directs _almost_
all calls to a single gateway -- the first gateway in the table --
though not 100%. There is also a marked tendency to send lots of
consecutive calls to the same gateway, even if it's not the first one,
though most of the time it is.
Has anyone experienced similar upon upgrading to 5.2?
Thanks much!
-- Alex
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda