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

Allow to configure the HttpClient maximumBackoffDuration #33

Merged
merged 1 commit into from
Mar 8, 2023

Conversation

eexit
Copy link
Contributor

@eexit eexit commented May 19, 2022

Hi there,

I work with @allan-simon, who reported this issue, and reducing the timeout is a bit useless if there's a retry mechanism we can't configure.

Our integration is sync so we can't afford blocking 17s+ for a retry that will most likely fail anyway.

The do/while is for when I want to set maximum_backoff_duration to 0, so it could at least try once.

@eexit eexit force-pushed the master branch 4 times, most recently from 5d32dbe to 8f1d2aa Compare May 20, 2022 13:32
@eexit
Copy link
Contributor Author

eexit commented Jun 29, 2022

Hello, any update on when this could be merged/released?

Thanks!

@allan-simon
Copy link

@EDsCODE is it possible to have your opinion on this PR ? :)

@phishy
Copy link

phishy commented Mar 8, 2023

This destroyed prod for me today. This definitely needs to be configurable.

@phishy
Copy link

phishy commented Mar 8, 2023

Using fork_curl seems to alleviate this. Any reason it's not the default?

@EDsCODE EDsCODE merged commit c5a38a2 into PostHog:master Mar 8, 2023
@phishy
Copy link

phishy commented Mar 8, 2023

@EDsCODE Are you aware of any caveats using fork_curl ?

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.

4 participants