2025-12-19, 09:18 PM
(This post was last modified: 2025-12-19, 11:13 PM by Ellermw. Edited 1 time in total.)
Ok so Pessimistic wasn't the move. It then causes query congestion, meaning if a library scan is in process, it locks/blocks UI queries... so you can't even load Jellyfin's home page.
Some of the errors from the logs when it was set to NoLock
Bash(journalctl -u jellyfin --since "2 minutes ago" 2>/dev/null | tail -30)
⎿ Dec 19 21:12:43 LXCJellyfin jellyfin[833181]: Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: UserDat
a.ItemId, UserData.UserId, UserData.CustomDataKey'.
Dec 19 21:12:43 LXCJellyfin jellyfin[833181]: at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
Going to try Optimistic now instead of Pessimistic for the DB Locking behavior
Also like to note that I have my parallel tasks limited to 2 for both.
Some of the errors from the logs when it was set to NoLock
Bash(journalctl -u jellyfin --since "2 minutes ago" 2>/dev/null | tail -30)
⎿ Dec 19 21:12:43 LXCJellyfin jellyfin[833181]: Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: UserDat
a.ItemId, UserData.UserId, UserData.CustomDataKey'.
Dec 19 21:12:43 LXCJellyfin jellyfin[833181]: at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
Going to try Optimistic now instead of Pessimistic for the DB Locking behavior
Also like to note that I have my parallel tasks limited to 2 for both.