Bug 1797934 - Client should propagate ping event from brick
Summary: Client should propagate ping event from brick
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-04 09:21 UTC by Pranith Kumar K
Modified: 2020-02-05 12:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-05 12:13:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 24093 0 None Merged protocol/client: Maintain connection to brick status 2020-02-05 12:13:39 UTC

Description Pranith Kumar K 2020-02-04 09:21:11 UTC 
Description of problem:
The current version of the code depends on the non-zero-port information to propagate ping event but as and when connection succeeds, port is set to zero in rpc layer. So ping event is never propagated to parent layers.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Worker Ant 2020-02-04 10:26:53 UTC 
REVIEW: https://review.gluster.org/24093 (protocol/client: Maintain connection to brick status) posted (#1) for review on master by Pranith Kumar Karampuri
Comment 2 Worker Ant 2020-02-05 12:13:41 UTC 
REVIEW: https://review.gluster.org/24093 (protocol/client: Maintain connection to brick status) merged (#3) on master by Pranith Kumar Karampuri
Note You need to log in before you can comment on or make changes to this bug.