From f89d5998fbfe1a0f683827f417ade21a7dccc907 Mon Sep 17 00:00:00 2001 From: JD Robertson <44848933+JD-Robertson@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:24:48 -0500 Subject: [PATCH] Cleanup RabbitMQ recovery documentation (#216) * Cleanup RabbitMQ recovery documentation * Cleanup * Mention delete --- getting-started/templates/systemlink-values.yaml | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/getting-started/templates/systemlink-values.yaml b/getting-started/templates/systemlink-values.yaml index 953205c9..574a8160 100644 --- a/getting-started/templates/systemlink-values.yaml +++ b/getting-started/templates/systemlink-values.yaml @@ -128,15 +128,21 @@ global: ## rabbitmq: ## Policy used when starting pods in the stateful set. - # - RabbitMQ pods must start in reverse shutdown order. - # To restore the cluster to a healthy state after an unexpected shutdown, temporarily set - # podManagementPolicy to "Parallel" and forceBoot to true. - # https://github.com/bitnami/charts/tree/main/bitnami/rabbitmq#recover-the-cluster-from-complete-shutdown + # - The "OrderedReady" podManagementPolicy must be used for the first deployment + # of the application. Once the application has been deployed, change the + # podManagementPolicy to "Parallel" to avoid synchronization issues when upgrading + # RabbitMQ instances. It will be necessary to manually delete the rabbitmq stateful + # set from the deployment prior to redeploying with the new setting. ## podManagementPolicy: "OrderedReady" # podManagementPolicy: "Parallel" clustering: ## Force cluster to boot after an unexpected shutdown (in an unexpected order). + # - If RabbitMQ fails to restart after an unexpected shutdown, setting foreceBoot to + # true temporarily may resolve the issue. The RabbitMQ maintainers recommend only + # setting this flag to recover from extraordinary circumstances. It should not be used + # for regular application maintenance. + # https://www.rabbitmq.com/docs/clustering#restarting ## forceBoot: false