[Bugs] [Bug 1373723] glusterd experiencing repeated connect/ disconnect messages when shd is down

bugzilla at redhat.com bugzilla at redhat.com
Fri Sep 30 13:27:30 UTC 2016


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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15532 committed in release-3.8 by Niels de
Vos (ndevos at redhat.com) 
------
commit ad9a1d1e8430388995f6a3fcd192ada7c9417a8d
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Sep 8 11:33:59 2016 +0530

    socket: pollerr event shouldn't trigger socket_connnect_finish

    If connect fails with any other error than EINPROGRESS we cannot get
    the error status using getsockopt (... SO_ERROR ... ). Hence we need
    to remember the state of connect and take appropriate action in the
    event_handler for the same.

    As an added note, a event can come where poll_err is HUP and we have
    poll_in as well (i.e some status was written to the socket), so for
    such cases we need to finish the connect, process the data and then
    the poll_err as is the case in the current code.

    Special thanks to Kaushal M & Raghavendra G for figuring out the issue.

    >Signed-off-by: Shyam <srangana at redhat.com>
    >Reviewed-on: http://review.gluster.org/15440
    >Smoke: Gluster Build System <jenkins at build.gluster.org>
    >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    >Reviewed-by: Raghavendra G <rgowdapp at redhat.com>

    Change-Id: Ic45ad59ff8ab1d0a9d2cab2c924ad940b9d38528
    BUG: 1373723
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/15532
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9oeP73Qzbo&a=cc_unsubscribe


More information about the Bugs mailing list