-
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
Proposal for Thanos Sharding. #1501
Conversation
Generally looks good, just some grammar and one consistency/cleanup type question. |
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.
Comments by @brancz look on point and the proposal LGTM besides one question. Thanks! This is definitely needed and will be very nice.
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.
Awesome! LGTM! 👍
2379f3f
to
19bfed0
Compare
This is not ready - I need to rework this to simplify and focus on sharding only but explain how it can be extended for more advanced use cases if needed. |
19bfed0
to
e568c3d
Compare
* `<name>` | ||
* `__block_objstore_bucket_endpoint` | ||
* `__block_objstore_bucket_name` | ||
* `__block_objstore_bucket_path` |
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.
This is a bit confusing to me. So let's say there will be a special __block_objstore_bucket_path
label, how can we manipulate it?
As I understand it we will be able to configure Thanos Store gateway to filter out folders from s3?
action: drop
regex: "folder_name"
source_labels:
- __block_objstore_bucket_path
Not sure how we can we do with __block_objstore_bucket_endpoint
, __block_objstore_bucket_name
as they will be constant on the time?
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.
Yes, for now the options are limited - maybe indeed we should limit this (:
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.
We can talk about those details on the PR I guess.
Signed-off-by: Bartek Plotka <bwplotka@gmail.com>
e568c3d
to
f7a0576
Compare
This should be good to go! |
Signed-off-by: Bartek Plotka <bwplotka@gmail.com> Signed-off-by: Giedrius Statkevičius <giedriuswork@gmail.com>
Signed-off-by: Bartek Plotka bwplotka@gmail.com
cc @jojohappy @mattrco @metalmatze