mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #1341] Re-Snapshot button is failing with core.models.Snapshot.DoesNotExist: Snapshot matching query does not exist #3838
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3838
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pirate on GitHub (Feb 3, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1341
Discussed in https://github.com/ArchiveBox/ArchiveBox/discussions/1340
Originally posted by gerroon January 31, 2024
@makew0rld commented on GitHub (Feb 17, 2025):
Seems like a duplicate of #1506
@pirate commented on GitHub (Feb 18, 2025):
Clsoing both as stale for now as this is a generic error that just indicates the db is overloaded, you should try running fewer URLs at a time or move your db to a faster drive. The most common cause is trying to store the index.sqlite3 on a slow HDD or smb mount. We make continuous performance improvements in every version, and locking contention should decline over time as we make ArchiveBox more efficient.
@makew0rld commented on GitHub (Feb 18, 2025):
Could URLs (or writes in general) not be queued to prevent this? I guess using something other than SQLite would work too.
@pirate commented on GitHub (Feb 18, 2025):
Both those options and more have already been extensively discussed in other issues, I don't want to repeat too much of it here but basically SQLite is plenty fast. It's not an issue with SQLite, it's a design choice that archivebox is single threaded because we're effectively rate limited by remote domains anyway. There are big performance improvements in the new betas that should eliminate most locking contention almost entirely.