[Bugs] [Bug 1418091] [RFE] Support multiple bricks in one process (multiplexing)

[bugzilla at redhat.com]

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



--- Comment #9 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16533 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit 0a0112b2c02a30bcb7eca8fa9ecb7fbbe84aa7f8
Author: Jeff Darcy <jdarcy at redhat.com>
Date:   Wed Feb 1 22:00:32 2017 -0500

    socket: retry connect immediately if it fails

    Previously we relied on a complex dance of setting flags, shutting
    down the socket, tearing stuff down, getting an event, tearing more
    stuff down, and waiting for a higher-level retry.  What we really
    need, in the case where we're just trying to connect prematurely e.g.
    to a brick that hasn't fully come up yet, is a simple retry of the
    connect(2) call.

    This was discovered by observing failures in ec-new-entry.t with
    multiplexing enabled, but probably fixes other random failures as
    well.

    Backport of:
    > Change-Id: Ibedb8942060bccc96b02272a333c3002c9b77d4c
    > BUG: 1385758
    > Reviewed-on: https://review.gluster.org/16510

    BUG: 1418091
    Change-Id: I4bac26929a12cabcee4f9e557c8b4d520948378b
    Signed-off-by: Jeff Darcy <jdarcy at redhat.com>
    Reviewed-on: https://review.gluster.org/16533
    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: Shyamsundar Ranganathan <srangana at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.