Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gRPC connection drop in fabric-nodejs #642

Open
tittuvarghese opened this issue Jan 13, 2023 · 8 comments
Open

gRPC connection drop in fabric-nodejs #642

tittuvarghese opened this issue Jan 13, 2023 · 8 comments

Comments

@tittuvarghese
Copy link

When I use fabric node sdk for invokes, at times getting the below connection drop errors and during retry it's getting executed without any issues.

2023-01-12T12:25:49.557Z - error: [Endorser]: sendProposal[peer2-org1.example.com:30002] - Received error response from: grpcs://peer2-org1.example.com:30002 error: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.557Z - error: [Endorser]: sendProposal[peer2-org1.example.com:30002] - rejecting with: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.558Z - error: [Endorser]: sendProposal[peer3-org0.example.com:30002] - Received error response from: grpcs://peer3-org0.example.com:30002 error: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.558Z - error: [Endorser]: sendProposal[peer3-org0.example.com:30002] - rejecting with: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.558Z - error: [Endorser]: sendProposal[peer3-org2.example.com:30002] - Received error response from: grpcs://peer3-org2.example.com:30002 error: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.558Z - error: [Endorser]: sendProposal[peer3-org2.example.com:30002] - rejecting with: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.558Z - error: [Endorser]: sendProposal[peer3-org1.example.com:30002] - Received error response from: grpcs://peer3-org1.example.com:30002 error: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.558Z - error: [Endorser]: sendProposal[peer3-org1.example.com:30002] - rejecting with: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.559Z - error: [Endorser]: sendProposal[peer2-org0.example.com:30002] - Received error response from: grpcs://peer2-org0.example.com:30002 error: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.559Z - error: [Endorser]: sendProposal[peer2-org0.example.com:30002] - rejecting with: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.559Z - error: [Endorser]: sendProposal[peer4-org2.example.com:30002] - Received error response from: grpcs://peer4-org2.example.com:30002 error: Error: 14 UNAVAILABLE: Connection dropped
2023-01-12T12:25:49.559Z - error: [Endorser]: sendProposal[peer4-org2.example.com:30002] - rejecting with: Error: 14 UNAVAILABLE: Connection dropped
peer=peer2-org0.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer3-org0.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer3-org1.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer2-org1.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer3-org2.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer4-org2.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer2-org0.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer3-org0.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer3-org1.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer2-org1.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer3-org2.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped
peer=peer4-org2.example.com:30002, status=grpc, message=14 UNAVAILABLE: Connection dropped

@bestbeforetoday
Copy link
Member

It might be the connections to the peers are being closed by something along the network path (like an ingress controller or firewall) if they are idle too long. If this is the case, configure appropriate gRPC keep-alive settings for your environment:

@tittuvarghese
Copy link
Author

it is passing through HAProxy and Nginx Ingress controller. Whenever connection drop happens, it drops for all peers in same time.

2 similar comments
@tittuvarghese
Copy link
Author

it is passing through HAProxy and Nginx Ingress controller. Whenever connection drop happens, it drops for all peers in same time.

@tittuvarghese
Copy link
Author

it is passing through HAProxy and Nginx Ingress controller. Whenever connection drop happens, it drops for all peers in same time.

@Ethereumx
Copy link

I am facing the same issue and no firewall is used

@bestbeforetoday
Copy link
Member

Is this an issue that has only started occurring after picking up a newer Node SDK version? If so, do you know the versions that worked and the one that is demonstrating problems? If not, do configuring appropriate keepalive settings solve it?

@bestbeforetoday
Copy link
Member

@tittuvarghese Did you have any luck solving the disconnection issues by configuring appropriate keep-alive and related gRPC settings?

@tittuvarghese
Copy link
Author

@bestbeforetoday I started getting stable connection after removing Haproxy from the connection path (tried different configs in haproxy but nothing worked out).

But sill I observe some drop connections / commit failures randomly at the orderer level. (This started coming when we distributed the orderer geographically. (between two different region with in the country))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants