Stability: registry, trigger-queue, postgres-egress, scheduler en otel-probes #203
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#203
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). Vijf kleinere maar reële gaten in één planbaar issue.
Bevindingen
dictenreplicas: 1. Restart maakt discovery leeg tot de volgende heartbeats.engine/services/capability-registry/app/main.pyrond 79-82.queue.SimpleQueuealsORCH_TRIGGER_EVENTS_ASYNC=true.engine/services/orchestrator/app/trigger_event_store.pyrond 45 en 247. Een burst kan de orchestrator OOMKill-en.psycopg.connectper request, zonder pool en zonderconnect_timeout/statement_timeout.engine/services/postgres/app/main.pyrond 330-344.engine/services/scheduler/app/main.pyrond 170, 584 en 760.engine/deploy/k8s/otel-collector-deployment.yaml.Gewenste uitkomst