[X] I searched open reports and couldn't find a duplicate
What happened?
We are storing an in-house conda channel on a NFS drive. After a recent upgrade from conda-build 3.27.0 to conda-index 0.5.0 (used conda index before, now python -m conda-index), we are facing problems with "database is locked" or "file is not a database" error messages from the sqlite3 module.
The sqlite docs list as first disadvantage "All processes using a database must be on the same host computer; WAL does not work over a network filesystem", which is both not satisfied in our scenario.
Can the journal mode be changed to SQLite's default DELETE (not sure about PRAGMA synchronous ) to allow NFS storage of the channel (and concurrent conda index from different client machines)?
Checklist
What happened?
We are storing an in-house conda channel on a NFS drive. After a recent upgrade from conda-build 3.27.0 to conda-index 0.5.0 (used
conda index
before, nowpython -m conda-index
), we are facing problems with "database is locked" or "file is not a database" error messages from the sqlite3 module.conda-index/index/common.py
usesThe sqlite docs list as first disadvantage "All processes using a database must be on the same host computer; WAL does not work over a network filesystem", which is both not satisfied in our scenario.
Can the journal mode be changed to SQLite's default
DELETE
(not sure aboutPRAGMA synchronous
) to allow NFS storage of the channel (and concurrentconda index
from different client machines)?Conda Info
No response
Conda Config
No response
Conda list
No response
Additional Context
No response