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
We are getting intermittent bal build issues from time to time due to random central call failures.
Seems like we have retryOnConnectionFailure enabled from okHTTP side. We need to evaluate on what occasions it retries and how many times it does that.
Most common failures we've observed as of now were 500, 502, 503 and connection resets for now. We need to see if retryOnConnectionFailure retries for such such cases, if not handle those separately.
If retryOnConnectionFailure doesn't work for such cases,I feel like having even a single retry should reduce these intermittent failures by a great margin.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered:
A similar client as the Central client is created with okHttp3 client. A service that always returns 500, 502, and 503 respectively for its resources is also created. I couldn't observe the client retrying for the resource calls mentioned above.
We will add retries manually.
Description
We are getting intermittent bal build issues from time to time due to random central call failures.
Seems like we have retryOnConnectionFailure enabled from okHTTP side. We need to evaluate on what occasions it retries and how many times it does that.
Most common failures we've observed as of now were 500, 502, 503 and connection resets for now. We need to see if retryOnConnectionFailure retries for such such cases, if not handle those separately.
If retryOnConnectionFailure doesn't work for such cases,I feel like having even a single retry should reduce these intermittent failures by a great margin.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: