Balancing Hyperledger fabric transactions (and queries) between 2 peer nodes

1/24/2020

I have a simple Hyperledger Fabric network with just 2 peers using Kubernetes. Peer 1 is having load issues and it periodically is respawning, which is a problem as it won't be restarted until a request is received. This first request returns timeout as it needs some time to start (I am using java chaincode)

I have seen that peer 2 gets no request or transaction from the orderer. How should I configure the orderer to balance transactions between both peers?

I also want to balance queries to the chaincode. I am using fabric Java SDK. What is the recommended approach to distribute the queries to both peers and not just to the first one? Currently, peer 2 is completely unused by Orderer or Java SDK client.

-- icordoba
hyperledger-fabric
hyperledger-fabric-sdk-java
kubernetes

0 Answers