Switching from feature-complete to errors-only leaves stale containers running and causes Kafka instability

[KimSeoYeon23]

Self-Hosted Version

nightly (self-hosted repo commit cb408ca)

CPU Architecture

aarch64

Docker Version

29.3.0

Docker Compose Version

v2.35.1-desktop.1

Machine Specification

• My system meets the minimum system requirements of Sentry

Installation Type

Fresh install

Steps to Reproduce

1. Install and start self-hosted Sentry with COMPOSE_PROFILES=feature-complete.
2. Let the full set of services start.
3. Change .env to COMPOSE_PROFILES=errors-only.
4. Restart the stack with Docker Compose.
5. Observe that previously created feature-complete services are still present/running instead of only the errors-only set.
6. Observe Kafka instability and downstream unhealthy services.

Expected Result

After switching to COMPOSE_PROFILES=errors-only, only the errors-only service set should run.

Previously created feature-complete services should not remain active, and the stack should come up cleanly without Kafka instability or web timeouts.

Actual Result

Previously created feature-complete services remained present after switching to COMPOSE_PROFILES=errors-only.

This led to an unstable stack:

• Kafka entered a startup / restart loop
• taskbroker and multiple snuba-* consumers became unhealthy
• the web UI intermittently returned 504
• logs included kafka:9092 ... Connection refused and AllBrokersDown

This did not appear to be caused by insufficient Docker resources.

Environment:

• Docker Desktop on macOS
• CPU: 8
• Memory: 18 GB

The stack became stable only after fully removing the existing sentry-self-hosted containers and starting again with errors-only.

After full cleanup:

• kafka became healthy
• web became healthy
• nginx became healthy
• http://localhost:9000 returned 302 to /auth/login/

Event ID

No response

[aldy505]

3. Change .env to COMPOSE_PROFILES=errors-only.
4. Restart the stack with Docker Compose.
5. Observe that previously created feature-complete services are still present/running instead of only the errors-only set.

You're taking the wrong steps here. After you change .env to errors-only, you should re-run ./install.sh rather than just restarting the Docker stack. It wouldn't work because the restart does not see the changed COMPOSE_PROFILES. This is more of a Docker issue rather than a configuration issue.