CalvinBackup/OBLITERATUS
1
0
Fork 0
mirror of https://github.com/elder-plinius/OBLITERATUS.git synced 2026-08-30 14:40:38 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: align broker pending window with cold loads (#185)

Browse Source
This commit is contained in:
Joseph Magly
2026-08-29 01:36:37 -04:00
parent 02cafde149
commit d3533d382f
2 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deployment/systemd/ollama-unify-negotiator.service.d/70-obliteratus-loading-window.conf
+6
View File
@@ -0,0 +1,6 @@
[Service]
# A cold Qwen3.8-27B load can exceed the negotiator's five-minute pending
# transition deadline when the shared host is storage-bound. Keep the broker
# drained until OBLITERATUS reports ready, while its persistent heartbeat and
# fail-closed supervisor continue to enforce lease ownership.
Environment=OLLAMA_UNIFY_PENDING_TIMEOUT=7200
docs/deployment/shared-gpu-host.md
+7
View File
@@ -117,6 +117,13 @@ Environment=OBLITERATUS_RUN_ARCHIVE=/srv/obliteratus/run-archive
ExecStart=/srv/obliteratus/current/.venv/bin/obliteratus ui --host 127.0.0.1
```
The broker's absolute pending-transition deadline must also cover the largest
expected cold model load. Broker heartbeats renew lease ownership but do not
extend this fail-closed deadline. On the shared A100 host, install
`deployment/systemd/ollama-unify-negotiator.service.d/70-obliteratus-loading-window.conf`
to use the same 120-minute budget; otherwise a healthy storage-bound load is
revoked after the negotiator's five-minute default.
Create the archive before starting the service and make it writable only by the
service account (for example, owner `obliteratus`, mode `0750`). Every UI and
headless run receives a stable `run-*` ID and writes `manifest.json`,