grpc-node: Error: 14 UNAVAILABLE: Stream refused by server

Problem description

hi, when the request volume is large, there will be several such errors.

Error: 14 UNAVAILABLE: Stream refused by server

It is difficult to reproduce in my local environment

Environment

OS name, version and architecture: Alpine Linux 3.12
Node version: v14.18.1
@grpc/grpc-js: ^1.3.1,
@grpc/proto-loader: ^0.5.6,

Additional context

start server:

 this.server.bindAsync(address, this._credentials, (error, port) => {
                if (error) {
                    this.logger.error(error.message, port);
                    return reject(error);
                }
                this.server.start();
                this.logger.debug(`server started on address: ${address}`);
                resolve(true);
 });

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 19 (8 by maintainers)

Most upvoted comments

In case it’s helpful I just got this one time while running a Google Cloud Function which calls a Firestore in Datastore Mode database within it. (Same endpoint has processed millions of requests without running in to it before, though)

Trace:

Error: 14 UNAVAILABLE: Stream refused by server
    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:189:52)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
    at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:187:78
    at processTicksAndRejections (node:internal/process/task_queues:78:11)

bcjordan on Jul 6, 2022

I also want to mention that I will be off for the rest of the year. I will continue to look into this in January, but I do not expect to respond again until then.

murgatroid99 on Dec 16, 2021