Active-Active notifier using presence module

Ivan Ribakov via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <[email protected]>
I would like to configure 2 (or more) Kamailio to act as HA notifier cluster. I want subscriptions to survive complete node reboots so I'm looking at using presence module with DB replication, specifically: subs_db_mode = 3 and publ_cache = 0.

However while running some initial tests I came across the table locking issue (MySQL error 1100). I'm using MariaDB 10.11 with innoDB and default root user. Further research led me to an older thread (https://lists.kamailio.org/pipermail/sr-users/2019-January/104288.html) and the documentation for db_table_lock_type parameter that states that it should be set to 0 (no locking) when using DB-only mode (subs_db_mode = 3).

My question is - if presence module is not using table locks, what prevents notify processes on 2 or more different nodes to simultaneously process the same presentity record and issue multiple notifies for the same subscription?
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.