hedera-sdk-js: gRPC service failed with status: TIMEOUT

Description

In 50 out of 3000 transactions more or less , we are getting this error:

GrpcServiceError: gRPC service failed with status: TIMEOUT
    at Timeout._onTimeout (...\@hashgraph\sdk\lib\channel\NodeChannel.cjs:111:20)
    at listOnTimeout (node:internal/timers:564:17)
    at process.processTimers (node:internal/timers:507:7) {
  status: GrpcStatus { _code: 17 }
}

It happens either sending NFTs, either sending Hbar or inclusive creating a new Account. We are executing it in BackEnd in Node.js

This is a big problem for us and we’re having big troubles with our Clients because of this.

This is happening in v2.18.5 , v2.19.1 and v2.19.2 . In these versions which are the ones I tested in all of them happens.

Steps to reproduce

1- .addNftTransfer() 2- .addHbarTransfer() 3- Generating a new Account in Hedera

Additional context

No response

Hedera network

mainnet

Version

2.19.1

Operating system

None

About this issue

Original URL
State: closed
Created a year ago
Comments: 21 (11 by maintainers)

Most upvoted comments

@mshakeg Yes, it is in milliseconds. All the timings in the SDKs are in milliseconds.

ochikov on Apr 25, 2023

Just to let you know how we are going to fix it: Let’s say that you are hitting Node 10 which contains 3 different IPs. If one of the IPs is not responsible and we are not getting any error (timeout), we will wait some default time and then try to process the transaction through another Node. You now see the Timeout error because we are not marking this node as unhealthy. Now we will mark it, your execution will be awaiting to switch for a new node and try to process the transaction, BUT this transaction will not be discarded, but trying to process it. I will give you a beta release version when we are ready. Roughly estimated time for this fix will be tonight/tomorrow morning.

ochikov on Jan 26, 2023