Scenario
Chunk rejections persist on one distributor after scale-out and secret rotation.
A Loki ring expands and one distributor still rejects chunks because it cached the retired gossip secret
New ingesters join, but one distributor still computes ring membership using a stale memberlist secret.
What to check first
- Identify the primary failure signal in the The New Writers Joined the Ring and One Distributor Kept Listening for the Password That Was Retired at the Door scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect memberlist caches before restarting the cluster.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field