From 91d5cce8ad74825dd872aa408833281ff7025c55 Mon Sep 17 00:00:00 2001 From: Owen Diehl Date: Wed, 3 Nov 2021 09:49:04 -0400 Subject: [PATCH] index-gw sts doc fix. closes #4583 (#4616) * index-gw sts doc fix. closes #4583 * Update docs/sources/operations/storage/boltdb-shipper.md Co-authored-by: Kaviraj Co-authored-by: Kaviraj --- docs/sources/operations/storage/boltdb-shipper.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/operations/storage/boltdb-shipper.md b/docs/sources/operations/storage/boltdb-shipper.md index c745db7774..a9d9fe191a 100644 --- a/docs/sources/operations/storage/boltdb-shipper.md +++ b/docs/sources/operations/storage/boltdb-shipper.md @@ -104,7 +104,7 @@ This avoids running Queriers and Rulers with a disk for persistence. Disks can b To run an Index Gateway, configure [StorageConfig](../../../configuration/#storage_config) and set the `-target` CLI flag to `index-gateway`. To connect Queriers and Rulers to the Index Gateway, set the address (with gRPC port) of the Index Gateway with the `-boltdb.shipper.index-gateway-client.server-address` CLI flag or its equivalent YAML value under [StorageConfig](../../../configuration/#storage_config). -Within Kubernetes, if you are not using an Index Gateway, we recommend running an Index Gateway as a StatefulSet with persistent storage for downloading and querying index files. This will obtain better read performance, and it will avoid using node disk. +When using the Index Gateway within Kubernetes, we recommend using a StatefulSet with persistent storage for downloading and querying index files. This can obtain better read performance, avoids [noisy neighbor problems](https://en.wikipedia.org/wiki/Cloud_computing_issues#Performance_interference_and_noisy_neighbors) by not using the node disk, and avoids the time consuming index downloading step on startup after rescheduling to a new node. ### Write Deduplication disabled