Scenario
A single Loki distributor rejects chunks after scale-out and gossip key rotation.
A Loki scale-out adds ingesters and one distributor still rejects chunks because the memberlist secret stayed stale in cache
The ring changes are valid, but one distributor still trusts the previous gossip key and never accepts the new view.
What to check first
- Identify the primary failure signal in the The New Writers Joined the Ring and One Distributor Kept Listening for Yesterday's Password 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
Compare memberlist secrets and 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