From 76648bf69a6206183e4a1cdd85437ca986e6ec08 Mon Sep 17 00:00:00 2001 From: Reinaldy Rafli Date: Sun, 10 May 2026 21:16:23 +0700 Subject: [PATCH 1/2] chore(self-hosted): use politically neutral wording --- develop-docs/self-hosted/troubleshooting/kafka.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/develop-docs/self-hosted/troubleshooting/kafka.mdx b/develop-docs/self-hosted/troubleshooting/kafka.mdx index 67a2be956acb39..a4669fd7e48fcf 100644 --- a/develop-docs/self-hosted/troubleshooting/kafka.mdx +++ b/develop-docs/self-hosted/troubleshooting/kafka.mdx @@ -140,10 +140,10 @@ This option is as follows ([reported](https://github.com/getsentry/self-hosted/i Unlike the proper solution, this involves resetting the offsets of all consumer groups and all topics. -#### Nuclear option +#### Hard recovery - The _nuclear option_ is to remove all Kafka-related volumes and recreate them. **This will cause data loss.** You'll lose any unprocessed events from the last 24 hours. Events that have already been processed and persisted in ClickHouse will remain safe. + The _hard recovery_ is to remove all Kafka-related volumes and recreate them. **This will cause data loss.** You'll lose any unprocessed events from the last 24 hours. Events that have already been processed and persisted in ClickHouse will remain safe. 1. Stop the instance: From adcfc437b5ee27178dbae4c4faf89a1dfad1e5a0 Mon Sep 17 00:00:00 2001 From: Reinaldy Rafli Date: Wed, 13 May 2026 05:10:56 +0700 Subject: [PATCH 2/2] Update kafka.mdx Co-authored-by: Shannon Anahata --- 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 a4669fd7e48fcf..203476bec8069c 100644 --- a/develop-docs/self-hosted/troubleshooting/kafka.mdx +++ b/develop-docs/self-hosted/troubleshooting/kafka.mdx @@ -143,7 +143,7 @@ Unlike the proper solution, this involves resetting the offsets of all consumer #### Hard recovery - The _hard recovery_ is to remove all Kafka-related volumes and recreate them. **This will cause data loss.** You'll lose any unprocessed events from the last 24 hours. Events that have already been processed and persisted in ClickHouse will remain safe. + When all other options have failed, your best option is to remove all Kafka-related volumes and recreate them. **This will cause data loss.** You'll lose any unprocessed events from the last 24 hours. Events that have already been processed and persisted in ClickHouse will remain safe. 1. Stop the instance: