Skip to content
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.

Back off when a listener is dead #32

Closed
mezis opened this issue Sep 2, 2016 · 1 comment
Closed

Back off when a listener is dead #32

mezis opened this issue Sep 2, 2016 · 1 comment

Comments

@mezis
Copy link
Contributor

mezis commented Sep 2, 2016

When delivery fails (on whichever error, e.g. 500 from the subscriber), we instantly retry (when the batching deadline has been reached).

Implement a backoff mechanism so that retries happen after 100ms, 200ms, 400ms, 800ms, 1600ms, 3200ms, 6400ms (no higher).

Not a bug per se (everything still works) but this keeps the watch process busy retrying, at 100% CPU. It does still service oether subscribers.

@mezis mezis added the bug label Sep 2, 2016
@mezis
Copy link
Contributor Author

mezis commented Dec 6, 2016

@mezis mezis closed this as completed Dec 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant