Bug 1365085 - Enable accessing internals of transport through meta
Summary: Enable accessing internals of transport through meta
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-08 12:21 UTC by Raghavendra G
Modified: 2019-06-20 04:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-20 04:57:02 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Raghavendra G 2016-08-08 12:21:22 UTC 
Description of problem:
Currently meta prints only the protocol/client and not the transport associated with it. This bug tracks the effort to print diagnostic information of transport (whether socket is connected to remote peer, identifier, ports/address of two endpoints etc)

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Amar Tumballi 2019-06-20 04:57:02 UTC 
Not picked up in a long time, closing as DEFERRED to indicate the status. Will come back to this after couple of releases.
Note You need to log in before you can comment on or make changes to this bug.