Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

index-gw sts doc fix. closes #4583 #4616

Merged
merged 2 commits into from
Nov 3, 2021
Merged

index-gw sts doc fix. closes #4583 #4616

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a7545d
index-gw sts doc fix. closes #4583
owen-d Nov 2, 2021
a3af38d
Update docs/sources/operations/storage/boltdb-shipper.md
owen-d Nov 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sources/operations/storage/boltdb-shipper.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 by not using the node disk, and avoids the time consuming index downloading step on startup after rescheduling to a new node.
owen-d marked this conversation as resolved.
Show resolved Hide resolved

### Write Deduplication disabled

Expand Down