8 Mar
2017
8 Mar
'17
1:30 a.m.
On 08/03/2017 01:36, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Those were the observations described by the one opening this thread and
then I responded with why I think it happens so, but as I wrote, I
haven't really checked the source code yet.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
So, I expect kamailio wil reuse the connection
between kamailio1 and
kamailio2. The tcp manager process selects the least loaded tcp worker
when a new connection is accepted, and the worker start consuming the
packets on it until there is nothing to be read on it. The reason behind
this approach is that a proxy is typically sending back a 100 trying or
some other provisional response while handling the request. If the
connection is very busy, so there are always packets to read, then
practically the selected tcp workers keeps processing the traffic and
never release the tcp connection back to the tcp manager.
So, for example, if k2
is a presence server and k1 is forwarding
subscribes/publish requests to it, only one process at k2 would be
processing them since the tcp connection between k1 and k2 is reused?