-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
docs: Document Thanos Sharding #1922
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
--- | ||
title: Sharding | ||
type: docs | ||
menu: thanos | ||
slug: /sharding.md | ||
--- | ||
|
||
# Background | ||
|
||
Currently all components that read from object store assume that all the operations and functionality should be done based | ||
on **all** the available blocks that are present in the certain bucket's root directory. | ||
|
||
This is in most cases totally fine, however with time and allowance of storing blocks from multiple `Sources` into the same bucket, | ||
the number of objects in a bucket can grow drastically. | ||
|
||
This means that with time you might want to scale out certain components e.g: | ||
|
||
* Compactor: Larger number of objects does not matter much, however compactor has to scale (CPU, network, disk, memory) with number of Sources pushing blocks to the object storage. | ||
|
||
# Relabelling | ||
|
||
Similar to [promtail](https://github.com/grafana/loki/blob/master/docs/promtail.md#scrape-configs) this config will follow native | ||
[Prometheus relabel-config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) syntax. | ||
|
||
The relabel config defines filtering process done on **every** synchronization with object storage. | ||
|
||
We will allow potentially manipulating with several of inputs: | ||
|
||
* External labels: | ||
* `<name>` | ||
|
||
Output: | ||
|
||
* If output is empty, drop block. | ||
|
||
By default, on empty relabel-config, all external labels are assumed. | ||
|
||
Example usages would be: | ||
|
||
* Drop blocks which contains external labels cluster=A | ||
|
||
```yaml | ||
- action: drop | ||
regex: "A" | ||
source_labels: | ||
- cluster | ||
``` | ||
|
||
* Keep only blocks which contains external labels cluster=A | ||
```yaml | ||
- action: keep | ||
regex: "A" | ||
source_labels: | ||
- cluster | ||
``` | ||
|
||
We can shard by adjusting which labels should be included in the blocks. | ||
|
||
# Time Partitioning | ||
|
||
For store gateway, we can specify `--min-time` and `--max-time` flags to filter for what blocks store gateway should be responsible for. | ||
|
||
More details can refer to "Time based partitioning" chapter in [Store gateway](components/store.md). |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Explain same for Store GW