Using sqlite3, thousands of "database is locked" warnings in logs

[solracsf]

Discussed in #2615

^{Originally posted by solracsf August 28, 2022}
When using Litestream, there are some parameters that can be optimized : https://litestream.io/tips/

Is there any way to pass PRAGMA parameters? Could this be an enhancement?

This would avoid lines like:

juicefs[634272] <WARNING>: Transaction succeeded after 3 tries (3.671605ms), inodes: [1], last error: database is locked [sql.go:654]

See https://github.com/mattn/go-sqlite3/blob/master/README.md#connection-string
If this is already possible, document it.

[solracsf]

I've tested a mount with

sqlite3://juicefs.db?_journal_mode=WAL&_busy_timeout=5000&_synchronous=NORMAL

and it seem to work flawlessly, PR at #2647.

But LOCK warnings still happening.

<WARNING>: Transaction succeeded after 3 tries (1.968603ms), inodes: [], last error: database is locked [sql.go:654]

[solracsf]

Let me add this here that could help for a better handling of these:
mattn/go-sqlite3#632 (comment)

[davies]

Can you add -q to ignore these warning?

[solracsf]

Why hide them instead of avoid them? 🥴