-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sqlite cache issues with network file system and/or concurrent conda_index processes #177
Closed
2 tasks done
Labels
source::community
catch-all for issues filed by community members
type::bug
describes erroneous operation, use severity::* to classify the type
Comments
meesepyter
added
the
type::bug
describes erroneous operation, use severity::* to classify the type
label
Aug 6, 2024
dholth
added
the
source::community
catch-all for issues filed by community members
label
Aug 23, 2024
Sounds feasible. We may have to check that it doesn't interfere with local multiprocess indxing. |
Any update on this? I'm having to use the old Background: Using on a docker container, volume mapped from a network drive:
|
We would accept a PR that removes the "enable WAL" pragma Would you have any use for a postgresql database instead of sqlite? |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
source::community
catch-all for issues filed by community members
type::bug
describes erroneous operation, use severity::* to classify the type
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
The text was updated successfully, but these errors were encountered: