From 22e4b7c9ac1666c841d3dac1fb0a85e9c34bc0d7 Mon Sep 17 00:00:00 2001 From: Oleg Zaytsev Date: Wed, 16 Oct 2024 16:28:30 +0200 Subject: [PATCH] Improve MimirGossipMembersEndpointsOutOfSync runbook command Signed-off-by: Oleg Zaytsev --- docs/sources/mimir/manage/mimir-runbooks/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/mimir/manage/mimir-runbooks/_index.md b/docs/sources/mimir/manage/mimir-runbooks/_index.md index ab23693a68..0ca3da6130 100644 --- a/docs/sources/mimir/manage/mimir-runbooks/_index.md +++ b/docs/sources/mimir/manage/mimir-runbooks/_index.md @@ -936,7 +936,7 @@ How to **investigate**: - Check the number of endpoints matching the `gossip-ring` service: ``` - kubectl --namespace get endpoints gossip-ring + kubectl --namespace get endpoints gossip-ring -ojson | jq '.subsets[].addresses | length' ``` - If the number of endpoints is 1000 then it means you reached the Kubernetes limit, the endpoints get truncated and you could be hit by [this bug](https://github.com/kubernetes/kubernetes/issues/127370). Having more than 1000 pods