[tempo-distributed] set unique cluster_label for tempo-distributed memberlist #3058
+14
−3
Conversation
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
hobbsh
requested review from
mapno,
swartz-k,
BitProcessor and
faustodavid
as code owners
hobbsh
force-pushed
the
unique-cluster-label-tempo-distributed
branch
from
2172e80
to
6b769f0
Compare
hobbsh
changed the title
Signed-off-by: Wylie Hobbs <[email protected]>
Signed-off-by: Wylie Hobbs <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
joe-elliott
force-pushed
the
unique-cluster-label-tempo-distributed
branch
from
e403476
to
ecdf88c
Compare
joe-elliott
approved these changes
Nov 6, 2024
zalegrala
approved these changes
Nov 6, 2024
|
Thanks @hobbsh. Sorry these took so long to get merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addressing grafana/tempo#2766 where Loki/Tempo ingesters can join each other's ring because cluster_label seems to be defaulted to something common to both components. This change should mitigate the issue in the future.