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

Corrupt Ingester pod name in the ring #8034

Open
rishabhkumar92 opened this issue May 2, 2024 · 1 comment
Open

Corrupt Ingester pod name in the ring #8034

rishabhkumar92 opened this issue May 2, 2024 · 1 comment

Comments

@rishabhkumar92
Copy link

Describe the bug

We encounted a incident where we saw corrupt Ingester pod name in the ring for couple of pods.
There was character flip(c-k) in the name of pod.

To Reproduce

Steps to reproduce the behavior:

Reproduction of issue might be an issue as it was one off behavior, describing version and other details:

  1. Mimir version - 2.10.5
  2. Distributor/Rulers saw corrupt pod name in the ring and we saw some % of write and read failure which was expected.

Expected behavior

Pod name should be correct.

Environment

  • Infrastructure: Kubernetes

Additional Context

We uses memberlist which uses gossip based protocol for discovering pods. During time of corruption we did see some degraded probes(counter_memberlist_degraded_probe) around that time but that doesn't explain why pod were named in wrong way.

e.g: we say teleskope-kortex-ingester-zone-c-p-sequoia-204, correct name should be telescope-cortex-ingester-zone-c-p-sequoia-204

@rishabhkumar92
Copy link
Author

rishabhkumar92 commented May 3, 2024

Screenshot 2024-05-02 at 5 41 29 PM

Attaching screenshot describing memberlist tcp packet received errors around that time. cc: @krajorama

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant