read ECONNRESET in @grpc/grpc-js but not in grpc package
- Dominant language
- TypeScript
- Stars
- 4.8k
- Forks
- 716
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 10
Description
Description:
we were using @grpc/grpc-js package in the Kubernetes cluster with the alpine image, recently we got the chance to test in production. Sparingly we are observing the read ECONNRESET on the client-side with no logs on the server-side. We switched to an older version of @grpc/grpc-js--1.2.4 but still the error was observed.
In one of the microservices, we used grpc package with nestjs. that service never gave read ECONNRESET. so migrated all the microservices to grpc@1.24.6 package and now we do not face the read ECONNRESET error. The client takes a pretty good amount of time to connect to the server around like 2secs 3secs but no read ECONNRESET error is observed.
Environment:
- OS name, version and architecture: [e.g. Linux Ubuntu 18.04 amd64 Alpine ]
- docker image node:14.16.1-alpine
- Kubernetes istio load balancing
- Node version 14.16.1
-@grpc/proto-loader: 0.5.6
Earlier package: @grpc/grpc-js
New package: grpc@1.24.6
please tell any more details to add.
Contributor guide
Assessment
This issue has not been assessed yet.