[asterisk-bugs] [JIRA] (ASTERISK-29775) CPU spike

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257128#comment-257128 ] 

Asterisk Team commented on ASTERISK-29775:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> CPU spike
> ---------
>
>                 Key: ASTERISK-29775
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29775
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge, Channels/chan_local
>    Affects Versions: 16.22.0, 18.8.0
>         Environment: Ubuntu 18 and also Ubuntu 20
>            Reporter: Dan Cropp
>            Severity: Major
>
> We use AMI to do the following.  I don't think it's AMI causing the issue, but mentioning it.
> Create 2 ConfBridges (A and B)
> Create a Local channel 1234.  
> Add one end of the local channel 1234;1 to ConfBridge A.
> Add the other end of local channel 1234;2 to ConfBridge B.
> Create another Local channel 5678.
> Add one end of local channel 5678;2 to ConfBridge B.
> Now on local channel 5678;1, we execute a Record.
> The CPU spikes at this point.  I suspect the code is in some loop with processing the multiple calls with the ConfBridge.
> Even when the Record completes, the CPU is still running 95+%.  The top PIDs are all asterisk running CPU% 95-96%, others four are 10-20%.
> Basically, the box becomes so bogged down it runs into problems and can't process other things.
> Even if I remove local channel 5678;2 from ConfBridge B, the CPU stays running at peak.
> Once either ConfBridge has the calls kicked or either end of the local channel 1234 is removed from either ConfBridge, the CPU issue is resolved.
> While local channels like this doesn't make sense.  We originally found this because we had PJSIP calls in different ConfBridges but needed the ConfBridges to be connected with a local channel.  All was fine until a customer started requiring us to have separate recording for each participant in one of the bridge.  That's when we started adding local channels as each participant joined and began recording.
> By eliminating the PJSIP calls in the sample, it eliminates areas to look at.



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