Has anyone else been seeing sporadic errors like these from the dgraph-js grpc client recently?
13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: read ETIMEDOUT 13 INTERNAL: Failed to start HTTP/2 stream with error: The session has been destroyed
We’ve seen this with two dgraph-js versions…
…in both of our Dgraph Cloud environments:
- A single dedicated Dgraph Cloud instance running Dgraph v20.11.2-rc1-25-g4400610b2
- A high-availability Dgraph Cloud cluster running Dgraph v20.11.2-rc1-29-gff3c84328
I opened a Jira ticket with Dgraph support, but they haven’t responded in 6 days, so I have nowhere else to turn! This is killing us right now. These periodic timeouts seem to block all queries until the dgraph-js client resets itself.
Any help, ideas, thoughts, or recommendations would be appreciated. We’re desperate for a solution.