-
Notifications
You must be signed in to change notification settings - Fork 83
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
improve unhealthy status management #1208
Comments
also adding, separating freezing and unhealthy as currently they are coupled. we need to map the various areas we currently freeze/emit unhealthy and according to that decide what each flow does |
AFAIU, the freeze state is for unrecoverable errors
what use cases of recoverable unhealthy cases do we have? |
@mtsitrin one example would be skew (which require pausing, but may recover after e.g DA/settlement is reachable) |
right now unhealthy status is set by sending an unhealthy event. this is an issue in case we want to automatically recover from unhealthy status and it is required to refactor the logic to allow that.
The text was updated successfully, but these errors were encountered: