[asterisk-bugs] [JIRA] (ASTERISK-27014) configurable busy_timeout in sqlite backends

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27014:
------------------------------------------

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

> configurable busy_timeout in sqlite backends
> --------------------------------------------
>
>                 Key: ASTERISK-27014
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27014
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>            Reporter: Marek Cervenka
>
> sqlite is not designed for concurrency
> workarounds are wal - https://www.sqlite.org/wal.html . can be specified
> when creating DB with "pragma journal_mode=wal"
> and
> busy_timeout https://www.sqlite.org/c3ref/busy_timeout.html . MUST be
> specified per connection
> busy_timeout is hardcoded in queue_log and cel sqlite backends
> sqlite3_busy_timeout(db->handle, 1000);
> we prepared patch where this parameter can be configured



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