# Meet with random "Unhandled error: \[Stream with ID \[1027\] was closed by peer with code NO\_ERROR(0x00)\]"

**URL:** <https://discuss.akka.io/t/meet-with-random-unhandled-error-stream-with-id-1027-was-closed-by-peer-with-code-no-error-0x00/10302>\
**Category:** Akka gRPC\
**Tags:** grpc\
**Created:** [May 6, 2023, 12:05pm UTC](https://discuss.akka.io/t/meet-with-random-unhandled-error-stream-with-id-1027-was-closed-by-peer-with-code-no-error-0x00/10302 "2023-05-06T12:05:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhenglaizhang](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.akka.io/zhenglaizhang/32/3021_2.png) [@zhenglaizhang](https://discuss.akka.io/u/zhenglaizhang)\
**Post date:** [May 6, 2023, 12:05pm UTC](https://discuss.akka.io/t/meet-with-random-unhandled-error-stream-with-id-1027-was-closed-by-peer-with-code-no-error-0x00/10302/1 "2023-05-06T12:05:07Z")

</div>

Hi,

I have below setup in our k8s production environment:

client → envoy engress → envoy ingress → grpc-server-app

and today one of the grpc-server-app pod throws 5xx errors for one seconds, and logs error `Unhandled error: [Stream with ID [1027] was closed by peer with code NO_ERROR(0x00)]`

And at the same time client side throws `StatusRuntimeException msg=UNAVAILABLE: upstream connect error or disconnect/reset before headers. reset reason: overflow`

Could anybody help share any insight how can I proceed my investigation? It seems related with connection management or buffer management.

---

<div class="post-metadata">

**Author:** ![johanandren](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.akka.io/johanandren/32/85_2.png) [@johanandren](https://discuss.akka.io/u/johanandren)\
**Post date:** [May 8, 2023, 9:29am UTC](https://discuss.akka.io/t/meet-with-random-unhandled-error-stream-with-id-1027-was-closed-by-peer-with-code-no-error-0x00/10302/2 "2023-05-08T09:29:43Z")

</div>

I think it is something like your envoy proxy closing a HTTP/2 stream in a somewhat unexpected/abrupt way. Probably not critical. Not sure exactly what would cause envoy to do that, maybe the instance is crashing, shut down, or the connection/stream reached some timeout or limit inside envoy making it shut down with “overflow” as reason.

With Akka gRPC 2.3.0+ the peer-disconnect log is downgraded to a warning instead of an error on the server side, since it is not really critical.

---

<div class="post-metadata">

**Author:** ![zhenglaizhang](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.akka.io/zhenglaizhang/32/3021_2.png) [@zhenglaizhang](https://discuss.akka.io/u/zhenglaizhang)\
**Post date:** [May 8, 2023, 12:17pm UTC](https://discuss.akka.io/t/meet-with-random-unhandled-error-stream-with-id-1027-was-closed-by-peer-with-code-no-error-0x00/10302/3 "2023-05-08T12:17:36Z")

</div>

Many thanks Johan for the insight! Yes I am now inspecting the envoy settings to if something is related.