Stability: queue worker stopt na AMQP-fout terwijl probes groen blijven #201
Labels
No labels
prio/P1
prio/P2
prio/P3
status/leftover
status/new
status/parked
type/feature
type/ops
type/research
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MeshFlowsGPL/meshflows#201
Loading…
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?
Context
Stability review (2026-09-22).
Bevindingen
engine/services/orchestrator/app/queue_worker.pyrond 199-226: éénconnect_robusten daarnaasync for message, zonder outer reconnect-loop. De RabbitMQ-trigger inrabbitmq/app/main.pyheeft die loop wel.test -f /tmp/queue-worker-ready. Dat bestand wordt bij startup gezet en niet verwijderd bij disconnect.engine/deploy/k8s/orchestrator-worker-small-deployment.yamlrond 137-145.Impact
Na een channel-fout stopt de consumer. De pod blijft Ready. Berichten stapelen op de queue.
Gewenste uitkomst