CODEWITHSUNDEEP
hyperledger-fabrichyperledger-caliper
Gowthami
Gowthami

Reputation: 3

EndorseError: 2 UNKNOWN: too many requests for /gateway.Gateway, exceeding concurrency limit (500) in Hyperledger Caliper

I executed Hyperledger Fabric test network and it had no errors. When I benchmarked its performance with Hyperledger Caliper tool, it was successful. But when the transactions count is increased to 800 or 1000 or above it throws the below error,

2023.02.13-11:49:56.059 error [caliper] [connectors/peer-gateway/PeerGateway]   Failed to perform submit transaction [Admin_createPatient] using arguments [Client3_CAR557,Toyota,S,brown,Shotaro,29,123456890],  with error: EndorseError: 2 UNKNOWN: too many requests for /gateway.Gateway, exceeding concurrency limit (500)

To rectify the error I changed the value of gatewayService to 2500 from its default value 500, but still the error not rectified.

limits:

    concurrency:
        # endorserService limits concurrent requests to endorser service that handles chaincode deployment, query and invocation,
        # including both user chaincodes and system chaincodes.
        endorserService: 2500
        # deliverService limits concurrent event listeners registered to deliver service for blocks and transaction events.
        deliverService: 2500
        # gatewayService limits concurrent requests to gateway service that handles the submission and evaluation of transactions.
        gatewayService: 2500

Upvotes: 0

Views: 275

Answers (1)

david_k
david_k

Reputation: 5868

In the error message I assume that it was updated to say 2500 ? If not then the change wasn't picked up. If it was picked up then you will need to increase the value further. The number corresponds to in flight transactions, so you can only have that many transactions submitted and not committed being processed. This should track with the unfinished transaction count that caliper outputs during a benchmark run.

Upvotes: 0

Related Questions