Caused by 👍 Rejecting broadcast of normal message from 22.22.22.22:40548 with SERVICE_UNAVAILABLE 👍

[FoxCao]

### orderer error: orderer.common.broadcast] ProcessMessage -\u003e WARN 4717d\u001b[0m [channel: zlpchannel] Rejecting broadcast of normal message from 22.22.22.22:40548 with SERVICE_UNAVAILABLE: rejected by Order: no Raft leader\n","stream":"stderr","time":"2022-08-13T02:16:08.016000153Z"

### fabric-sdk-java error: error-2022-08-13.log:Caused by: java.lang.Exception: Channel zlpchannel failed to place transaction a822bbb44ef3d887bcc2b40a019afa7efa69ssss4adf5f9ab46aaf40b827ad7c on Orderer. Cause: UNSUCCESSFUL.

[Param-S]

As the error described, rejected by Order: no Raft leader, there is an issue with the orderering service nodes, there is no quorum. Can you check whether all the orderers in the consenters set is running and quorum(leader) is established. We can check these details in the orderer log.

[FoxCao]

Thanks for your answer , orderering service nodes wrok well now , but the leader selection spent 5 seconds, the issue happened when user send a proposal to orderer by fabric-sdk-java during selection , how should this situation be handled.

[Param-S]

I am wondering whether the time taken(5 secs) to select the leader is normal or can be improvised. we can take a look at the orderers log. @andrew-coleman @yacovm if the leader election takes more time,is there a way the client(peer gateway) to know and cache or retry the ordering request.

[FoxCao]

Thanks for your answer

I am wondering whether the time taken(5 secs) to select the leader is normal or can be improvised. we can take a look at the orderers log. @andrew-coleman @yacovm if the leader election takes more time,is there a way the client(peer gateway) to know and cache or retry the ordering request.

Thanks for your answer.

[yacovm]

5 seconds is normal.