Skip to content
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

Error: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error) #813

Closed
penguinsource opened this issue Apr 9, 2021 · 1 comment
Labels
api: datastore Issues related to the googleapis/nodejs-datastore API. priority: p2 Moderately-important priority. Fix may not be included in next release. status: duplicate Duplicate. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@penguinsource
Copy link

penguinsource commented Apr 9, 2021

  1. Is this a client library issue or a product issue?
    This is a client library issue.

  2. Did someone already solve this?
    I have seen several posts about it but no solution so far. I am looking to understand the root cause so I know how to avoid it best.

  3. Do you have a support contract?
    No

The error is as follows and it comes up frequently and it's a big problem!

Error: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)
    at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:176:52)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:342:141)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:305:181)
    at process.nextTick (/workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:124:78)
    at process._tickCallback (internal/process/next_tick.js:61:11)
  code: 13,
  details: 'Received RST_STREAM with code 2 (Internal server error)',
  metadata: Metadata { internalRepr: Map {}, options: {} },
  note:
   'Exception occurred in retry method that was not classified as transient' }"
  • It occurs mostly on GET calls but I don't see many other patterns emerging otherwise. It happens way too often for a database library to be considered stable, unfortunately. Is there any solution or any workaround?

Environment details

  • OS: App Engine servers
  • Node.js version: 12.13.0
  • npm version: 6.12.0
  • @google-cloud/datastore version: 6.3.1
@product-auto-label product-auto-label bot added the api: datastore Issues related to the googleapis/nodejs-datastore API. label Apr 9, 2021
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 10, 2021
@crwilcox crwilcox added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Apr 19, 2021
@crwilcox
Copy link
Contributor

I am marking this as a duplicate of #679. Please add any context there if you believe what you have experienced isn't captured.

@slo-stat-bot slo-stat-bot bot removed the 🚨 This issue needs some love. label Apr 19, 2021
@crwilcox crwilcox added the status: duplicate Duplicate. label Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: datastore Issues related to the googleapis/nodejs-datastore API. priority: p2 Moderately-important priority. Fix may not be included in next release. status: duplicate Duplicate. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

3 participants