[asterisk-bugs] [JIRA] (ASTERISK-29505) res_pjsip: Expires all contacts from realtime table, even if table is shared across multiple servers

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-29505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-29505:
--------------------------------------

    Summary: res_pjsip: Expires all contacts from realtime table, even if table is shared across multiple servers  (was: pjsip contact handling should only process the current asterisk system)

> res_pjsip: Expires all contacts from realtime table, even if table is shared across multiple servers
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29505
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29505
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 18.4.0, 18.5.0
>            Reporter: Andrew Yager
>
> In a multi-server environment with PJSIP using realtime tables, each asterisk server validates and expires all contacts, even if the server is not the active server (based on the systemname).
> Each server with access to the contacts table will independently try to expire contacts at expiration time.
> This has the effect of creating frequent deadlocks on MySQL environments in high volume contact environments (maybe around 1500+) unnecessarily.
> While the specific behaviour that is here is probably complex, it seems that:
> a) only one server should expire contacts, and this should ideally be the system that actually inserted the record
> b) if that system is unavailable, I'm not sure what I think the correct behaviour should be, but given a server will not show a contact that it is not the "owner" of it probably should just do nothing



--
This message was sent by Atlassian JIRA
(v6.2#6252)