Bug 1452114 - Add logs to identify whether disconnects are voluntary or due to network problems
Summary: Add logs to identify whether disconnects are voluntary or due to network prob...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: rpc
Version: 3.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milind Changire
QA Contact:
URL:
Whiteboard:
Depends On: 1426125
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-18 11:32 UTC by Milind Changire
Modified: 2017-11-07 10:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1426125
Environment:
Last Closed: 2017-11-07 10:37:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2017-05-18 11:51:55 UTC
REVIEW: https://review.gluster.org/17332 (rpc: log more about socket disconnects) posted (#1) for review on release-3.8 by Milind Changire (mchangir)

Comment 2 Milind Changire 2017-05-18 17:23:02 UTC
Description of problem:

One of the common problems we encounter are frequent connects/disconnects. Frequent disconnects can be either:

1. voluntary where the process calls a shutdown (2)/close (2) on an otherwise healthy socket connection.
2. involuntary where we get a POLLERR event from network.

While debugging this class of issues, it would help if can identify whether a particular disconnect falls into which of the two above categories. We need to add enough log messages to help us classify.

Comment 3 Niels de Vos 2017-11-07 10:37:57 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


Note You need to log in before you can comment on or make changes to this bug.