-
Notifications
You must be signed in to change notification settings - Fork 69
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
HTTP 500 errors should be retried #504
Comments
@symphony-elias i am a newbie to open source contribution, can i start working on this issue. |
No problem @SivaTharun, your contribution will be very welcome! Do you need any help before starting? |
Thanks @symphony-thibault for following up, i just need to know how to reproduce the above scenario, if you can point me to a unit test, which asserts for the 500 error from DatafeedAsyncLauncherService class (or) you can point to me to the resource for reproducing the above exception. |
We recently noticed that the DatafeedLoop was crashing with `500` errors returned from Agent. This is something we initially stated that we did not wanted to retry on this specific status. Now we do, as it has actually been raised by some customers.
We recently noticed that the DatafeedLoop was crashing with `500` errors returned from Agent. This is something we initially stated that we did not wanted to retry on this specific status. Now we do, as it has actually been raised by some customers.
Bug Report
During maintenance windows, when pod, km or agent is down, HTTP calls can result in HTTP 500. Such calls need to be retried.
For instance, on one of our bots, we got:
Expected Result:
HTTP 500 errors should be retried, see: https://github.com/finos/symphony-bdk-java/blob/main/symphony-bdk-http/symphony-bdk-http-api/src/main/java/com/symphony/bdk/http/api/ApiException.java#L81
Actual Result:
HTTP 500 errors lead to bot failing.
The text was updated successfully, but these errors were encountered: