You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.
We need to handle adapter failures in a systematic way. Whether an adapter panics, always returns errors, or constantly times out, we need to have a clear detection, tracking, and recovery plan. If we try to "reboot" the adapter a few times and things still fail, then we can take the adapter out of the running permanently until the operator tells us otherwise.
We need to architect this health-checking & tracking environment for maximum robustness at runtime. Let's spec out the model and implement the support needed.
The text was updated successfully, but these errors were encountered:
We need to handle adapter failures in a systematic way. Whether an adapter panics, always returns errors, or constantly times out, we need to have a clear detection, tracking, and recovery plan. If we try to "reboot" the adapter a few times and things still fail, then we can take the adapter out of the running permanently until the operator tells us otherwise.
We need to architect this health-checking & tracking environment for maximum robustness at runtime. Let's spec out the model and implement the support needed.
The text was updated successfully, but these errors were encountered: