Skip to content

Fix ingestion-only worker setup and default concurrency - #5917

Merged
warwickschroeder merged 3 commits into
masterfrom
warwick/ingestion-only-setup-refusal
Sep 25, 2026
Merged

warwickschroeder merged 3 commits into
masterfrom
warwick/ingestion-only-setup-refusal

Conversation

@warwickschroeder

@warwickschroeder warwickschroeder commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

What this fixes

An ingestion-only worker started with --setup-and-run ran the primary's full setup, and one started without a concurrency setting failed to start. Setup now refuses a worker, and a worker defaults to a concurrency of 10 like the primary. The refusal still prints a stack trace.

  • --setup and --setup-and-run refuse when combined with --error-ingestion-only, before provisioning anything.
  • A worker with no concurrency setting starts with the primary's default of 10.
  • The help text says a worker runs no setup.

Tests

  • ServiceControl.UnitTests/Hosting (new): argument parsing keeps the worker flag, and setup refuses a worker.
  • ServiceControl.AcceptanceTests/Recoverability/When_hosting_error_ingestion_only: a worker with no concurrency setting starts and receives with 10, on PostgreSQL and SQL Server.

@warwickschroeder
warwickschroeder merged commit cca1e62 into master Sep 25, 2026
36 checks passed
@warwickschroeder
warwickschroeder deleted the warwick/ingestion-only-setup-refusal branch September 25, 2026 08:05
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.

2 participants