-
Notifications
You must be signed in to change notification settings - Fork 617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[grpc-js] Error: 13 INTERNAL: Received RST_STREAM with code 0 #1532
Comments
Same issue here. With nodejs v10, and with no load. |
You say Regarding the error itself, the message indicates that the server unexpectedly closed the stream before the client considered it to be complete. The code |
thank you @murgatroid99 I'll have a repro repo up in a bit. the exception is not being thrown when one switches out the client to use the native deprecated |
I faced the same problem. You need to make sure your call method path starts with '/' just like below.
Having only |
any further progress on this? we have an issue with this error code as well. |
As I said before, reproduction code for this bug would help figure out what's happening. If you can share some that would be great. |
if it helps, we had these errors when running on GKE (google cloud's kubernetes engine), when under high load and resulting memory pressure. |
@chroth7 you basically just described our setup as well. We are running on GKE, with relatively high load, and subscribing to a long standing stream. I'll go back and check resource monitoring, but I was considering running just on a high-spec GCE to see if it might be a resource thing. Thanks for the thoughts and I'll post back in here if that helps out for us as well. |
I am seeing this as well. I am running a Typescript React App with a node.js server. The server is throwing this error fairly regularly. Something like once an hour. I also get this similar error: I had a crash on my site on Monday where I was not able to read or write the database and I am trying to figure out if its related. These are the 3 types of errors I am receiving of this type:
|
Does anybody know where to lookup for what each code means? |
happens calling a gRPC/go micro-service intermittently after a wait. So use case is like this:
grpc-js: 1.4.2 |
FWIW I have observed this specific error message when the server took longer than 60 seconds to respond. At 60s the client throws this error. I am using default settings for everything whatever they may be (e.g. no custom deadline specified). |
If it will help, I'm developing grpc protocol using nghttp2-lib.(C++) I found that if server sent ping to client, but client didn't response ping-ack to server, the server will send RST_STREAM with code 0 after sending the trailer. |
The server is always supposed to send an RST_STREAM with code 0 after sending trailers. That is expected and should not cause an error. This error occurs when the server sends an RST_STREAM with code 0 without sending trailers. |
@murgatroid99 I enabled debug trace in gRPC framework. Below is the difference between grpc-client and my client(called as nghttp2-grpc-client for convenience). Sames RST_STREAM with code 0 will not send if ping is normally response from client. |
I checked the spec again and I was mistaken. An RST_STREAM is not needed/expected after the server sends trailers. I notice in your first trace log that the line that corresponds to sending the RST_STREAM comes 6 seconds after the line that corresponds to sending trailers. And it seems to be more related to the BDP probe than to the individual stream. So I would guess that if the stream took longer to complete, the server would send the RST_STREAM before the trailers. |
For you guys how are using Kubernetes. Please check your Istio Sidecar. In my case, the traffic to GRCP client was blocked by the Istio Sidecar. After I disable the Istio Sidecar with annotation, it's working fine now. |
I get the same error with firebase emulator. Here are my firebase dependencies :
My initialization code is the following
The code that triggers the error is the following:
I saw some people updated firebase-functions to get it to work, but it seems this doesn't apply for me as I'm already at version 9. Here's the error I receive: |
had the same issue |
Problem description
grpc-js
client is throwing the following exception under high load:Reproduction steps
I have a repro repository in the works and will update with the link.
Environment
Additional context
The text was updated successfully, but these errors were encountered: