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

Disable backoffs max_elapsed_time functionality #305

Merged
merged 1 commit into from
Mar 11, 2021
Merged

Conversation

thomaseizinger
Copy link
Contributor

This config setting makes backoff stop retrying if we didn't get an
error within this timeframe.
For us, this results in backoff not actually doing anything.

The connection to kraken is very long-running. It might be active
for hours without failing. However, the default value for
max_elapsed_time is set to 15 minutes. As such, once the connection
fails any time after that, backoff doesn't actually retry the operation
but just gives up.

Fixes #303.

This config setting makes backoff stop retrying if we didn't get an
error within this timeframe.
For us, this results in backoff not actually doing anything.

The connection to kraken is very long-running. It might be active
for hours without failing. However, the default value for
`max_elapsed_time` is set to 15 minutes. As such, once the connection
fails any time after that, backoff doesn't actually retry the operation
but just gives up.

Fixes #303.
Copy link
Member

@da-kami da-kami left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! That explains why we never ran into a retry. I should have dug into backoff more thoroughly :)

@thomaseizinger
Copy link
Contributor Author

Thank you! That explains why we never ran into a retry. I should have dug into backoff more thoroughly :)

I was also very surprised by this behaviour and I am considering opening a discussion issue on backoff to remove it or at least change the default. It is not intuitive IMO.

@da-kami
Copy link
Member

da-kami commented Mar 11, 2021

bors r+

@bors bors bot merged commit b956f36 into master Mar 11, 2021
@bors bors bot deleted the no-max-backoff-time branch March 11, 2021 06:00
@thomaseizinger
Copy link
Contributor Author

Opened a discussion issue on backoff here: ihrwein/backoff#39

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

Successfully merging this pull request may close these issues.

Kraken websocket stream closes connection unexpectedly
3 participants