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

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-27014:
------------------------------------------------

Change 5695 merged by Jenkins2:
Sqlite3: make busy_timeout configurable.

[https://gerrit.asterisk.org/5695|https://gerrit.asterisk.org/5695]

> 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
>    Affects Versions: 13.15.0, 14.4.0, GIT
>            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)