Allow configuring Sentry taskworker concurrency via env (#4149)

* Allow configuring Sentry taskworker concurrency via env

* Update comment for SENTRY_TASKWORKER_CONCURRENCY ENV
This commit is contained in:
Kliachin Aleksei 2026-02-04 13:04:48 +08:00 committed by GitHub
parent 940074a527
commit 16982c307f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 1 deletions

2
.env
View File

@ -9,6 +9,8 @@ SENTRY_EVENT_RETENTION_DAYS=90
SENTRY_BIND=9000
# Set SENTRY_MAIL_HOST to a valid FQDN (host/domain name) to be able to send emails!
# SENTRY_MAIL_HOST=example.com
# Parallel taskworker processes (higher values increase memory usage; >32 not recommended)
SENTRY_TASKWORKER_CONCURRENCY=4
SENTRY_IMAGE=ghcr.io/getsentry/sentry:nightly
SNUBA_IMAGE=ghcr.io/getsentry/snuba:nightly
RELAY_IMAGE=ghcr.io/getsentry/relay:nightly

View File

@ -745,7 +745,7 @@ services:
command: run taskworker-scheduler
taskworker:
<<: *sentry_defaults
command: run taskworker --concurrency=4 --rpc-host=taskbroker:50051 --health-check-file-path=/tmp/health.txt
command: run taskworker --concurrency=$SENTRY_TASKWORKER_CONCURRENCY --rpc-host=taskbroker:50051 --health-check-file-path=/tmp/health.txt
healthcheck:
<<: *file_healthcheck_defaults
vroom: