-
Notifications
You must be signed in to change notification settings - Fork 24
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
[GT-152] timeout causes ssm to crash #228
[GT-152] timeout causes ssm to crash #228
Conversation
Working through https://stackoverflow.com/a/70994400 may resolve the weirdness of this PR showing already merged commits, it worked for GOCDB/gocdb#447. |
8f86972
to
93faef4
Compare
'Applied Rebase' - Squashed the commits into one. |
0c4e83d
to
93faef4
Compare
f6d3288
to
b53510a
Compare
But this clearly isn't the case if you look at the log in #214. The exception type raised is |
Note: Findings' shows that it seems there is an issue with older version of AMS when For ref: |
5807085
to
cb3b43e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you address my comment, and rebase the code, then I should be able to slip this into version 3.3.0. 👍🏻
4fc943c
to
bb6445a
Compare
I've double checked that these exceptions are available in the AMS lib 0.5.4 and 0.5.1, as used on apel-preprod and apel prod, respectively. |
bb6445a
to
83e91ca
Compare
@Sae126V Do check that you've pulled the latest from |
When we make use of
AmsHttpRequests
provided by the AMS itself,pull_sub.
is a POST request and it under the hood uses_retry_make_request()
where it tries to make an attempt for retries.In our case, retry =3:
If enabled (retry > 0), multiple subscription pulls will be tried in case of problems/glitches with the AMS service.
Because we are using the
ArgoMessagingService
class under the hood, it is making use ofrequests
lib. So timeouts (one of the API error status, requests.exceptions.ReadTimeout) from AMS (HTTP 408) or load balancer (HTTP 408 and 504) should be handled byAmsBalancerException,
AmsConnectionException,
AmsTimeoutException.
Resolves #214 .