Describe the bug
After network issues within our clusters we found, that ingesters were not able to join ring so we had to manually remove them.
There are multiple issues, describing this behavior, eg #8615 and #14847 .
Suggested fix would be to add autoforget_unhealthy flag to ingester config by default, as there seems to be no downsides for it.
Expected behavior
Unhealthy ingester leaving their ring after a timeout.
Environment:
Kubernetes 1.27
Describe the bug
After network issues within our clusters we found, that ingesters were not able to join ring so we had to manually remove them.
There are multiple issues, describing this behavior, eg #8615 and #14847 .
Suggested fix would be to add
autoforget_unhealthyflag to ingester config by default, as there seems to be no downsides for it.Expected behavior
Unhealthy ingester leaving their ring after a timeout.
Environment:
Kubernetes 1.27