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
This was noticed in "fresh" measurements where the logic is to try to fetch the bodies in this order:
From disk
From the list of collectors specified in the OTHER_COLLECTOR setting
From s3
For some reason if one of the OTHER_COLLECTORS is unreachable, the connection doesn't timeout in time, leading to a failure in retrieving the measurement.
We should look into either setting the urllib3 connection pool timeout or understand how we can make sure the failure is properly triggered so it doesn't stay hanging.
This was noticed in "fresh" measurements where the logic is to try to fetch the bodies in this order:
OTHER_COLLECTOR
settingFor some reason if one of the OTHER_COLLECTORS is unreachable, the connection doesn't timeout in time, leading to a failure in retrieving the measurement.
We should look into either setting the urllib3 connection pool timeout or understand how we can make sure the failure is properly triggered so it doesn't stay hanging.
See:
The text was updated successfully, but these errors were encountered: