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 detect if an adapter has stop being responsive by tracking execution timeouts.
Ideally, we maintain per-adapter configuration state with the max execution time allowed for calls into the adapter. The critical call to check is the runtime HandleXXX call, but it may be best to impose a timeout on all calls into adapters.
When a timeout is found to be triggered, we should log the occurrence. If a timeout happens too frequently, we should move the adapter into a "bozo" queue and stop scheduling requests for it.
The text was updated successfully, but these errors were encountered:
We need to detect if an adapter has stop being responsive by tracking execution timeouts.
Ideally, we maintain per-adapter configuration state with the max execution time allowed for calls into the adapter. The critical call to check is the runtime HandleXXX call, but it may be best to impose a timeout on all calls into adapters.
When a timeout is found to be triggered, we should log the occurrence. If a timeout happens too frequently, we should move the adapter into a "bozo" queue and stop scheduling requests for it.
The text was updated successfully, but these errors were encountered: