| Summary: | ASTERISK-26229: [patch] app_voicemail: Add taskprocessor alert level options. | ||
| Reporter: | Alexei Gradinari (alexei gradinari) | Labels: | |
| Date Opened: | 2016-07-22 16:37:32 | Date Closed: | 2017-09-28 15:49:38 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_voicemail/IMAP |
| Versions: | 13.10.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | On heavy loaded system with IMAP or DB storage,
'app_voicemail' taskprocessor queue could reach 500 scheduled tasks. It could happen when IMAP or DB server died or not reachable. It could happen on startup when there are many (thousands) realtime endpoints configured with unsolicited mwi. If taskprocessor queue reached high level, the alert is triggered and the pjsip/distributor stops processing new requsts. The patch adds 2 new 'general' configuration options to tune taskprocessor alert levels: 'tps_queue_high' - Taskprocessor high water alert trigger level. 'tps_queue_low' - Taskprocessor low water clear alert level | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-07-22 16:37:32.662-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. | ||