You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.
In #508 , logic was added to retry requests. There is a delay added between retries if the request is a POST. Would it be suitable to suitable to add that delay for all HTTP methods?
The use-case I'm finding is try a GET request too early, before influxdb has finished starting. I'm therefore getting a Connection refused returned straight away. Even with a high number of retries (50), the lack of delay causes them to cycle through too quickly.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
In #508 , logic was added to retry requests. There is a delay added between retries if the request is a
POST
. Would it be suitable to suitable to add that delay for all HTTP methods?The use-case I'm finding is try a
GET
request too early, before influxdb has finished starting. I'm therefore getting aConnection refused
returned straight away. Even with a high number of retries (50), the lack of delay causes them to cycle through too quickly.The text was updated successfully, but these errors were encountered: