zib/Veskslop-t
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Queue the smallest backfill jobs first and show queued state

Browse Source
This commit is contained in:
Fisto
2026-09-17 09:05:22 +02:00
parent 6ae2ff5ab3
commit c6a16a63f7
4 changed files with 22 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/media-scraper.md
+4 -3
View File
@@ -158,9 +158,10 @@ Previews run after every walk:
before their previews were cached. One job per chat groups every paused, done, or failed scrape
of that chat, so a paused-and-resumed scrape stays in one job. Jobs run one at a time, in
batches, and report pending/cached/failed counts, per-kind pending, throughput, and an ETA. The
Bot tab drives them: **Start backfill**, per-job Start/Pause, and **Pause all**. On daemon boot
jobs start automatically when the Backfilling setting **Start automatically on daemon boot** is
on.
Bot tab drives them: **Start backfill**, per-job Start/Pause, and **Pause all**. Jobs with the
least pending work start first, so small chats clear instead of waiting behind a long one; a job
that is started but waiting for the queue reads `queued`. On daemon boot jobs start automatically
when the Backfilling setting **Start automatically on daemon boot** is on.
- Transient fetch failures keep the row pending and count up `preview_attempts`. After the
**Tries before giving up** setting (default 3) the row is marked `unreachable after N attempt(s)`,
so dead hosts (Gfycat, Streamable) stop burning batches forever.