Every call should be get executed without gRPC related errors.
Actual behavior
Every now and then we get a No connection established error:
Error: No connection established
at Http2CallStream.call.on (/srv/functions/node_modules/@grpc/grpc-js/build/src/client.js:96:45)
at Http2CallStream.emit (events.js:194:15)
at Http2CallStream.EventEmitter.emit (domain.js:459:23)
at process.nextTick (/srv/functions/node_modules/@grpc/grpc-js/build/src/call-stream.js:75:22)
at process._tickCallback (internal/process/next_tick.js:61:11)
It encountered 8600 exact errors for the past week:
but we don't know how to set old grpc for functions.region(region).firestore to get rid of all these errors.
We are not sure if here is the right place to post this issue or the https://github.com/googleapis/nodejs-firestore. If this is the case, the please close this issue and we'll go and report it on the nodejs-firestore repo.
Were you able to successfully deploy your functions?
Related issues
https://github.com/googleapis/nodejs-firestore/issues/768
https://github.com/firebase/firebase-js-sdk/issues/1783
https://github.com/grpc/grpc-node/issues/1027
Version info
node: 10.15.1
firebase-functions: 3.3.0
firebase-tools: 7.6.0
firebase-admin: 8.6.0
Test case
Steps to reproduce
Expected behavior
Every call should be get executed without gRPC related errors.
Actual behavior
Every now and then we get a No connection established error:
It encountered 8600 exact errors for the past week:
For every other firestore operation, we used old
grpc
as described here https://github.com/googleapis/nodejs-firestore/issues/768#issuecomment-537311719:but we don't know how to set old grpc for
functions.region(region).firestore
to get rid of all these errors.We are not sure if here is the right place to post this issue or the https://github.com/googleapis/nodejs-firestore. If this is the case, the please close this issue and we'll go and report it on the nodejs-firestore repo.
Were you able to successfully deploy your functions?
No errors during functions deploy.