simplify general implementation
avoid deadlock due to a process trying to acquire same lock twice

Pre-Submission Checklist

[x ] Commit message has the format required by CONTRIBUTING guide
[ x] Commits are split per component (core, individual modules, libs, utils, ...)
[ x] Each component has a single commit (if not, squash them into one commit)
[ x] No commits to README files for modules (changes must be done to docbook files
in doc/ subfolder, the README file is autogenerated)

Type Of Change

[ x] Small bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds new functionality)
Breaking change (fix or feature that would change existing functionality)

Checklist:

PR should be backported to stable branches
Tested changes locally
Related to issue #XXXX (replace XXXX with an open issue number)

Description

On a timer, checking the availability of the master db used for writing and setting a status variable accordingly. In case the mdb_availability_control option is set, this status variable is consulted with no synchronization by each process when trying to do a write to the master db. As error mitigation, in case the per process handle associated with master db is NULL, p_usrlock recreates it. In case the per process handle is not NULL, Kamailio will try to recreate a broken connection by itself.

You can view, comment on, or merge this pull request online at:

https://github.com/kamailio/kamailio/pull/2399

Commit Summary

p_usrloc: reworking mdb_availability_control

File Changes

M src/modules/p_usrloc/p_usrloc_mod.c (23)
M src/modules/p_usrloc/p_usrloc_mod.h (6)
M src/modules/p_usrloc/ul_db.c (70)
M src/modules/p_usrloc/ul_db_watch.c (15)
M src/modules/p_usrloc/ul_db_watch.h (2)

Patch Links:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.