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
At random time, we do see Guard with the following error in the logs : HTTP Timeout with context deadline exceeded (Client.Timeout exceeded while awaiting headers).
The pattern identified is that all connections are failing for a period of ~12 to 17 min and starting to work again after that period.
I would like to raise a PR to enable HTTP/2 ping transport in the http.Client used by Guard. This will enforce the golang transport to do a HTTP/2 Ping every X amount of time and decide to either close or keep alive the connections in the pool.
The text was updated successfully, but these errors were encountered:
At random time, we do see Guard with the following error in the logs :
HTTP Timeout with context deadline exceeded (Client.Timeout exceeded while awaiting headers)
.The pattern identified is that all connections are failing for a period of ~12 to 17 min and starting to work again after that period.
It looks very similar to the following error we identified in Azure Golang SDK : Azure/azure-sdk-for-go#21346
I would like to raise a PR to enable HTTP/2 ping transport in the
http.Client
used by Guard. This will enforce the golang transport to do a HTTP/2 Ping every X amount of time and decide to either close or keep alive the connections in the pool.The text was updated successfully, but these errors were encountered: