Skip to content
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

Backoff strategy #99

Open
remimourgues opened this issue Aug 26, 2020 · 1 comment
Open

Backoff strategy #99

remimourgues opened this issue Aug 26, 2020 · 1 comment

Comments

@remimourgues
Copy link

remimourgues commented Aug 26, 2020

Hi,
When setting an exponential backoff strategy for the client, is there a way to distinguish between a failed connection (for exemple if the engine server is down) and an empty list of retrieved tasks ?
I found that the BackoffJobAcquisitionStrategy can suit the needs, but I can't see how to relate it with the client.
Thanks for the help

Edit : to be more precise, I would like to have the back off only when failing to connect to the server. If the connection is ok but the list of tasks is empty, then we retry ~immediately.

@kgeis
Copy link

kgeis commented Mar 26, 2021

It looks like this would be addressed by CAM-12816, tentatively scheduled for 7.16.

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

No branches or pull requests

2 participants