2 Jan
2019
2 Jan
'19
5:32 p.m.
Thx for the reply
Yes
Internal hash table diffenentelly stores info
But even it case of putting timeout to 0 it still grows in synthetic tests.
So looks like it will grows alsways because of deletes entries but creates
new and so on and so on...
So means it decrases "leak" but not fully
Is there some hidden function maybe to drop hast table o some ticky to do
this? (we are using oru ow algorinthm that garanties to use same node in
case of transaction)
ср, 2 янв. 2019 г. в 16:45, Richard Fuchs <rfuchs(a)sipwise.com>om>:
On 02/01/2019 07.45, Yuriy Gorlichenko wrote:
Hi!
Happy new year to all!!!
Look like I am first in this year wit hthe questions in this list :-).
I'm using stateless kamailio and RTPengnine to build some kind of the
stateless cluster
I found that kamailio keeps some data in the SHMEM in case of using
RTPengine module even if it is not a rtpengine_manage function but
offer/answer/delete
In this case if INVITE (offer) handled by 1-st kamailio in my cluster,
and BYE/CANCEL handled by second kamailio in the cluster - 1-st
kamailio (which has been used for offer) will hase kinda internal
"memory leak" (in SHMEM it never decrased)
At the rtpengine module source I found some transation dependencies
for the rtpengine_manage function but did not find for the
offer/answer/delete
I supposed these 3 functions just sending requests to the rtpnegine
with keys and not storing anything
So my question - is it possible to use RTPengine module in stateless
way to avoid internal "memory leak" because in my scenario I have big
chance never receive BYE/CANCEL on the machine that started handle
particular call
This is probably the module-internal hash table that is used to make
sure that signalling relating to the same call is always sent to the
same rtpengine instance. This hash table does have a configurable
timeout value (`hash_table_tout`, defaults to 1 hour), which makes it
possible to still use it in a way you've described. However, from the
code it's my understanding that timed out hash table entries are only
deleted when they're encountered during processing, so it's not entirely
deterministic that old entries are always deleted after they've timed
out. The RPC command `rtpengine.get_hash_total` can be used to inspect
the current size of the hash table.
Cheers
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users