From c76866b6a5fd8a3a86ad9c46e8d63629cfd6df36 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bartosz=20Stefa=C5=84czyk?= Date: Sun, 26 Dec 2021 21:05:35 +0100 Subject: [PATCH 1/2] Add note about mc-status under autopause section --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c1fe70d654e..69c5cb27d7e 100644 --- a/README.md +++ b/README.md @@ -1458,7 +1458,8 @@ Enable the Autopause functionality by setting: ``` Autopause is not compatible with `EXEC_DIRECTLY=true` and the two cannot be set together. - +You should use mc-health instead mc-status for healtcheck/readiness probe with autopause enabled. mc-status is known to have issues with paused servers. + The following environment variables define the behaviour of auto-pausing: * `AUTOPAUSE_TIMEOUT_EST`, default `3600` (seconds) describes the time between the last client disconnect and the pausing of the process (read as timeout established) From a718479916b17037af7c100134826bd220d7f425 Mon Sep 17 00:00:00 2001 From: Geoff Bourne Date: Sat, 1 Jan 2022 11:30:13 -0600 Subject: [PATCH 2/2] More positive wording --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 69c5cb27d7e..823ea6254fb 100644 --- a/README.md +++ b/README.md @@ -1458,8 +1458,9 @@ Enable the Autopause functionality by setting: ``` Autopause is not compatible with `EXEC_DIRECTLY=true` and the two cannot be set together. -You should use mc-health instead mc-status for healtcheck/readiness probe with autopause enabled. mc-status is known to have issues with paused servers. - + +> When configuring kubernetes readiness/liveness health checks with auto-pause enabled, be sure to reference the `mc-health` wrapper script rather than `mc-status` directly. + The following environment variables define the behaviour of auto-pausing: * `AUTOPAUSE_TIMEOUT_EST`, default `3600` (seconds) describes the time between the last client disconnect and the pausing of the process (read as timeout established)