[SR-Users] ndb_redis module fails after a while

Andrew Pogrebennyk apogrebennyk at sipwise.com
Fri Jan 13 09:28:40 CET 2012


Javi,
ndb_redis does not reconnect if the server closes connection on timeout. 
It should work if you set timeout to zero in server config. I thought 
that I created a ticket in the bugtracker for that before, but not sure, 
I can't find it right now.

On 13.01.2012 08:00, Javier Gallart wrote:
> Hi all
> 
> I have started making some tests with the ndb_redis module. So far we 
> have not stressed the module (no more than 5 HGET  commands/second at 
> maximum). It works well, but with at some point it starts failing. The 
> failures are easily found because the logs always show this:
> INFO: <core> [main.c:811]: INFO: signal 13 received
> After that the redis value is always null. If I restart kamailio it 
> starts working again.
> I've run kamailio with debug=4 but I haven't seen more useful 
> information. On the redis side, I could find nothing in the logs either, 
> the number of clientes connected is alway much less than the configured 
> maximum, Any idea?
> On the other hand, if I restart redis we need to restart kamailio to 
> restore the connections. Is the reconnection to redis on the roadmap?
> 
> Thanks in advance
> 
> Regards
> 
> Javi



More information about the sr-users mailing list