[Bugs] [Bug 1739336] New: Multiple disconnect events being propagated for the same child

[bugzilla at redhat.com]

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

            Bug ID: 1739336
           Summary: Multiple disconnect events being propagated for the
                    same child
           Product: GlusterFS
           Version: 5
                OS: Linux
            Status: NEW
         Component: rpc
          Keywords: Regression
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: amgad.saleh at nokia.com, amukherj at redhat.com,
                    bugs at gluster.org, ravishankar at redhat.com,
                    rgowdapp at redhat.com, rhinduja at redhat.com,
                    rhs-bugs at redhat.com, sankarshan at redhat.com,
                    sheggodu at redhat.com
        Depends On: 1703423, 1716979
            Blocks: 1739334, 1739335
  Target Milestone: ---
    Classification: Community



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

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

Description of problem:
Issue was reported upstream by a user via
https://github.com/gluster/glusterfs/issues/648

I'm seeing that if I kill a brick in a replica 3 system, AFR keeps getting
child_down event repeatedly for the same child. This seems to be a regression
in behaviour as it does not occur in rhgs-3.4.0. In 3.4.0, I get exactly one
GF_EVENT_CHILD_DOWN for 1 disconnect.

Version-Release number of selected component (if applicable):
rhgs-3.5 branch (source install)

How reproducible:
Always.

Steps to Reproduce:
1. Create a replica 3 volume and start it.
2. Put  a break point in __afr_handle_child_down_event() in glustershd process.
3. Kill any one brick.

Actual results:
The break point keeps getting hit once every 3 seconds or so repeatedly.

Expected results:
Only 1 event per one disconnect.

Additional info:
I haven't checked if the same happens for GF_EVENT_CHILD_UP as well. I think
this is regression that needs to be fixed. If this is not a bug please feel
free to close stating why.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1703423
[Bug 1703423] Multiple disconnect events being propagated for the same child
https://bugzilla.redhat.com/show_bug.cgi?id=1716979
[Bug 1716979] Multiple disconnect events being propagated for the same child
https://bugzilla.redhat.com/show_bug.cgi?id=1739334
[Bug 1739334] Multiple disconnect events being propagated for the same child
https://bugzilla.redhat.com/show_bug.cgi?id=1739335
[Bug 1739335] Multiple disconnect events being propagated for the same child
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.