From 26b8012eed92d4ec352e89b75cfbfc2010d9fd4c Mon Sep 17 00:00:00 2001 From: Jesse Kershaw Date: Thu, 4 Jun 2026 08:50:26 +0200 Subject: [PATCH] Remove totally destructive flag from troubleshooting guide The "hard recovery" option indicates that some data will be lost. However, the first instruction is to take down all services with the `--volume` flag which instructs docker to destroy _all_ named volumes, resulting in total data loss. The second step to remove just the `sentry-kafka` volume would be redundant since all volumes have been removed. This change removes the `--volume` option so that only the `sentry-kafka` volume will be removed. I have confirmed this fixed my issue without total data loss. --- develop-docs/self-hosted/troubleshooting/kafka.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/self-hosted/troubleshooting/kafka.mdx b/develop-docs/self-hosted/troubleshooting/kafka.mdx index 203476bec8069c..f5abdb3c9cbb29 100644 --- a/develop-docs/self-hosted/troubleshooting/kafka.mdx +++ b/develop-docs/self-hosted/troubleshooting/kafka.mdx @@ -148,7 +148,7 @@ Unlike the proper solution, this involves resetting the offsets of all consumer 1. Stop the instance: ```shell - docker compose down --volumes + docker compose down ``` 2. Remove the the Kafka volume: ```shell