[Bugs] [Bug 1426125] New: Add logs to identify whether disconnects are voluntary or due to network problems

bugzilla at redhat.com bugzilla at redhat.com
Thu Feb 23 09:19:38 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1426125

            Bug ID: 1426125
           Summary: Add logs to identify whether disconnects are voluntary
                    or due to network problems
           Product: GlusterFS
           Version: mainline
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: mchangir at redhat.com
                CC: bugs at gluster.org, rgowdapp at redhat.com,
                    rhinduja at redhat.com, rhs-bugs at redhat.com
            Blocks: 1426034



+++ This bug was initially created as a clone of Bug #1426034 +++

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.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2017-02-23
00:30:25 EST ---

This bug is automatically being proposed for the current release of Red Hat
Gluster Storage 3 under active development, by setting the release flag
'rhgs‑3.2.0' to '?'. 

If this bug should be proposed for a different release, please manually change
the proposed release flag.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1426034
[Bug 1426034] Add logs to identify whether disconnects are voluntary or due
to network problems
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list