Skip to content

fix: provisioner fails to restart after app reboot#101

Merged
itstauq merged 1 commit intomainfrom
itstauq/fix-provisioner-restart
Mar 4, 2026
Merged

fix: provisioner fails to restart after app reboot#101
itstauq merged 1 commit intomainfrom
itstauq/fix-provisioner-restart

Conversation

@itstauq
Copy link
Member

@itstauq itstauq commented Mar 4, 2026

Summary

  • Recovery paths in _ensure_provisioner_running tried RUNNING→STOPPED transition, but the state machine only allows RUNNING→STOPPING→STOPPED. The InvalidProvisionerTransitionError was silently swallowed, so ChromaDB never restarted on second boot.
  • Switched to force_status_update() for both recovery paths (dead process + alive-but-unhealthy process)
  • Added logger.exception() for swallowed provisioner startup errors

Test plan

  • Create a dataset with local_file type, verify ChromaDB starts
  • Stop the app, restart it — verify ChromaDB restarts and ingestion works
  • Kill the app abruptly (e.g. process-wick), restart — verify recovery

…ne violation

Recovery paths (dead process, alive-but-unhealthy process) tried to
transition RUNNING→STOPPED directly, but the state machine only allows
RUNNING→STOPPING→STOPPED. The resulting InvalidProvisionerTransitionError
was silently swallowed, so ChromaDB never restarted on second boot.

Use force_status_update() for these recovery paths and log swallowed
provisioner startup errors.
@itstauq itstauq merged commit f073a78 into main Mar 4, 2026
2 checks passed
@itstauq itstauq deleted the itstauq/fix-provisioner-restart branch March 4, 2026 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant