Skip to content

fix: don't start metrics server in duckdb-service workers#202

Merged
fuziontech merged 1 commit intomainfrom
fix/skip-metrics-in-workers
Feb 14, 2026
Merged

fix: don't start metrics server in duckdb-service workers#202
fuziontech merged 1 commit intomainfrom
fix/skip-metrics-in-workers

Conversation

@fuziontech
Copy link
Member

Summary

  • Workers are spawned by the control plane with --mode duckdb-service, and each was calling initMetrics() which tries to bind :9090
  • With the retry loop from fix(controlplane): eliminate systemd tracking warning and metrics port conflict #201, every worker would spin forever retrying the port — the CP holds it and never releases it
  • Fix: remove initMetrics() from the duckdb-service code path. The control plane owns the metrics endpoint; workers don't need their own

Test plan

  • All controlplane tests pass
  • Deploy and verify no metrics retry warnings from worker processes

🤖 Generated with Claude Code

Workers are spawned by the control plane with --mode duckdb-service.
Each worker was calling initMetrics() which tries to bind :9090, fighting
with the control plane and every other worker. The control plane already
owns the metrics endpoint — workers don't need their own.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@fuziontech fuziontech enabled auto-merge (squash) February 14, 2026 02:20
@fuziontech fuziontech merged commit 3191ee9 into main Feb 14, 2026
11 checks passed
@fuziontech fuziontech deleted the fix/skip-metrics-in-workers branch February 14, 2026 02:22
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