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.

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

Distributor ring not removing it's key from kvstore during shutdown. #5191

Closed
kavirajk opened this issue Jan 20, 2022 · 2 comments · Fixed by #5227
Closed

Distributor ring not removing it's key from kvstore during shutdown. #5191

kavirajk opened this issue Jan 20, 2022 · 2 comments · Fixed by #5227
Labels
type/bug Somehing is not working as expected

Comments

@kavirajk
Copy link
Contributor

Describe the bug
We found in our clusters, during rollout, the distributors that are leaving the ring failed to remove i'ts key from the underlying kvstore (consul in our case)
"unhealthy" on /distributor/ring status page.

To Reproduce
Steps to reproduce the behavior:
Happens on tip of Loki's main branch

Expected behavior
When distributor that is leaving the ring (during rollout for example) should also cleanup it's key from kvstore properly.

Environment:

  • Kubernetes

Related:

  • distributor ring introduced in this PR
@trevorwhitney
Copy link
Collaborator

@kavirajk I'm not sure the ring was added in #4938. I know that PR first exposed the page, but wasn't there always a distributor ring used for when limit enforcement strategy was set to global?

@kavirajk
Copy link
Contributor Author

@trevorwhitney yes you are absolutely right. Ring was there even before that PR. We found the issue is actually because of the subtle behavior of CAS operation on KV store the ring uses (consul in our case).

Explained in more detail in this issue on dskit repo.

@chaudum chaudum added the type/bug Somehing is not working as expected label Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Somehing is not working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants