I have had an opportunity now to push this into production and verify that it
works at a large scale. Thank you very much for the prompt response and fix,
Henning and Daniel! It is deeply appreciated.
—
Sent from mobile, with due apologies for brevity and errors.
> On Aug 13, 2019, at 9:42 AM,
Thanks, JR! That’s something to look at.
However, in this case probing is disabled.
—
Sent from mobile, with due apologies for brevity and errors.
> On Aug 13, 2019, at 9:40 AM, JR Richardson wrote:
>
> Hey Alex,
>
> After I recently upgraded, I had to include more response codes, 5.2 by
>
Hey Alex,
After I recently upgraded, I had to include more response codes, 5.2 by default
only 200 OK is accepted. I had some upstream carriers sending 405 and were
taken off-line as a result until I added that code in modparm:
modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=405")
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
Hi Alex,
there have been many changes to the modules between 5.1 and 5.2. I just
looked a bit to the code of dispatch.c and also the commits.
I noticed something in commit 3933a64c464acfb285e - there was a block
related to round-robin before which got removed in this refactoring (if
I analyze
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.
> On Aug 12, 2019, at 11:24 AM, Daniel-Constan
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
On 12.08.19 15:23, Alex Balashov wrote:
> Hi,
>
> I've got a proxy that does very basic ro
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 gateway
