[Asterisk-Dev] Unlocking the unlocked...

Guillermo Winkler gwinkler at inconcertcc.com
Tue Jun 28 21:45:03 MST 2005

    We're recording wav, mixing mp3. The retries patch is more a proof of concept (Usually for that server load, calling again ast_get_channel_by_name_locked finds the channel , that makes 20 retries).

I don't think a .conf variable will do, I think the list traversing functions needs some re-work considering that under heavy load this problem will get worst.

If more people thinks this issue should be addressed it can be followed up on mantis.


Date: Tue, 28 Jun 2005 20:14:06 -0400
From: mattf <mattf at vicimarketing.com>
Subject: RE: [Asterisk-Dev] Unlocking the unlocked...
To: 'Asterisk Developers Mailing List' <asterisk-dev at lists.digium.com>
<DB43F516702AAF4392AA45573F18181901267BAB at vicimail.vicimarketinggroup.com>

Content-Type: text/plain; charset="iso-8859-1"


Happens to us every day for the last year and a half. It's a hard disk
read/write speed issue for the recordings. We've keep our recording drives
on separate physical disks from everything else and we try to keep that
partition as defragged as possible and that does help reduce the
channel_walk_locked warnings and the associated periodic recording audio

I'm very interested in your experience with changing the number of retries
and your results as we have not tried that yet. 

What audio format do you record in(wav or gsm)?
What do you usually change the number of retries to and how are the results?

If this can help significantly, maybe a config variable in features.conf
would be in order?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20050628/16e1b84b/attachment.htm

More information about the asterisk-dev mailing list