Does anyone know of any issues running usrloc with DB backing ('location') in a multi-master DB-replicated environment? I am referring to plain usrloc, not p_usrloc.
I have such an environment set up with db_mode = 1 (immediate write-through) and have run into a problem where Kamailio occasionally stops writing to the location table for no apparent reason. I am wondering if this is because another Kamailio instance bound to the secondary replica is performing a DB sync as well, and at some point they collide in some sort of race condition. Would db_mode 2 fix? Would anything fix? Is this even the problem?
Hello,
On 7/3/12 8:03 PM, Alex Balashov wrote:
Does anyone know of any issues running usrloc with DB backing ('location') in a multi-master DB-replicated environment? I am referring to plain usrloc, not p_usrloc.
I have such an environment set up with db_mode = 1 (immediate write-through) and have run into a problem where Kamailio occasionally stops writing to the location table for no apparent reason. I am wondering if this is because another Kamailio instance bound to the secondary replica is performing a DB sync as well, and at some point they collide in some sort of race condition. Would db_mode 2 fix? Would anything fix? Is this even the problem?
is this like blocking or just not writing to db, but in memory everything is ok? iirc, all db failed operations should be reported as error to syslog, do you get any?
Cheers, Daniel
-
Alex Balashov -
Daniel-Constantin Mierla