search

adobe / helix-dispatch

A Helix microservice that retrieves content from multiple sources and delivers the best match
Apache License 2.0
4 stars 2 forks source link

FetchError: Stream closed with error code NGHTTP2_REFUSED_STREAM causes 500 #509

Open dominique-pfister opened 3 years ago

dominique-pfister commented 3 years ago

From time to time, we see the following error being reported by this service:

{
  inv:{
    invocationId:901af061-04ef-4a54-8b38-317d14ad25fd
    functionName:/helix-services/dispatch/4.11.3
    transactionId:Root=1-60f03fb7-286be3214b5797856ee62c28
    requestId:Cg7kuipCIAMEVLw=
 }
  level:error
  cdn:{
    url:https://theblog--adobe.hlx.page/en/publish/2015/dalfoxpathtest/03/are-you-using-social-audience-data-for-ad- 
    targeting-how-to-start.html
  }
  message:error while invoking fetchers: FetchError: Stream closed with error code NGHTTP2_REFUSED_STREAM
  timestamp:2021-07-15T14:01:28.402526558Z
}

This is being reported with a status code 500, though AFAICT, refusing a stream is not an abnormal condition, it simply indicates that some stream offered has been refused, so it might be enough to catch this specific error in this service with a warning.

Sample logs in coralogix: https://helix.coralogix.com/#/query-new/logs?id=2Ve00ULJvn5

dominique-pfister commented 3 years ago

Note, though, that I sometimes saw the very same error message in other services, where the real issue is another, causing this FetchError as a by-product.