Skip to content
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.

Introduce adapter timeout tracking #1499

Open
geeknoid opened this issue Oct 23, 2017 · 0 comments
Open

Introduce adapter timeout tracking #1499

geeknoid opened this issue Oct 23, 2017 · 0 comments
Assignees
Milestone

Comments

@geeknoid
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants