Bandwidth exhausted error keeps showing up

[jakeleventhal]

Environment details

• OS: macOS Catalina 10.15.5 Beta (19F53f)
• Node.js version: 13.7.0
• npm version: 6.13.6
• @google-cloud/firestore version: 3.7.4

Steps to reproduce

Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted
at Object.callErrorFromStatus (/api/node_modules/@grpc/grpc-js/src/call.ts:81)
at Object.onReceiveStatus (/api/node_modules/@grpc/grpc-js/src/client.ts:324)
at Object.onReceiveStatus (/api/node_modules/@grpc/grpc-js/src/client-interceptors.ts:439)
at Object.onReceiveStatus (/api/node_modules/@grpc/grpc-js/src/client-interceptors.ts:402)
at Http2CallStream.outputStatus (/api/node_modules/@grpc/grpc-js/src/call-stream.ts:228)
at Http2CallStream.maybeOutputStatus (/api/node_modules/@grpc/grpc-js/src/call-stream.ts:278)
at Http2CallStream.endCall (/api/node_modules/@grpc/grpc-js/src/call-stream.ts:262)
at ClientHttp2Stream.<anonymous> (/api/node_modules/@grpc/grpc-js/src/call-stream.ts:532)
at ClientHttp2Stream.emit (events.js:315)
at ClientHttp2Stream.EventEmitter.emit (domain.js:485)
at emitErrorCloseNT (internal/streams/destroy.js:76)
at processTicksAndRejections (internal/process/task_queues.js:84)

[schmidt-sebastian]

@jakeleventhal Thanks for reporting and sorry that you keep running into these issues. I hope that your error rate is at least going down.

As you are likely aware, we fixed a similar issue last year. The fix for this is part of Node 13.3 (nodejs/node#30774). There might be other problematic errors in the Node 13.7 HTTP2 stack or in our usage of it. If this keeps popping up, we can take a closer look at the network stack, but unfortunately I am personally rather swamped with other work at this point.

Do you mind letting us know how often you see these errors?

[jakeleventhal]

Not often, though it seems it came at about the same time as the RST_STREAM errors from #1023

[crwilcox]

@schmidt-sebastian any updates in this area?

[schmidt-sebastian]

No, unfortunately not. @jakeleventhal - If you are able to provide a reproduction for us, we can take another look. Unfortunately, we have to close this issue for now, as we would like to clean up stale issues.

[jakeleventhal]

I just searched my logs from 10/1/2020 to 12/05/20.
This doesn't show up at all. Closing is fine.