From ab458df415627049cf6f58f48300117f5e95d955 Mon Sep 17 00:00:00 2001 From: "Dustin C. Hatch" Date: Sun, 23 Jun 2024 09:53:36 -0500 Subject: [PATCH] v-m/vmstorage: Start pods in parallel By default, Kubernetes waits for each pod in a StatefulSet to become "ready" before starting the next one. If there is a problem starting that pod, e.g. data corruption, then the others will never start. This sort of defeats the purpose of having multiple replicas. Fortunately, we can configure the pod management policy to start all the pods at once, regardless of the status of any individual pod. This way, if there is a problem with the first pod, the others will still come up and serve whatever data they have. --- victoria-metrics/vmstorage.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/victoria-metrics/vmstorage.yaml b/victoria-metrics/vmstorage.yaml index f9b094f..216f1a6 100644 --- a/victoria-metrics/vmstorage.yaml +++ b/victoria-metrics/vmstorage.yaml @@ -29,6 +29,7 @@ spec: matchLabels: app.kubernetes.io/name: vmstorage app.kubernetes.io/component: vmstorage + podManagementPolicy: Parallel template: metadata: labels: