diff options
author | Jeff Darcy <jdarcy@redhat.com> | 2017-02-01 22:00:32 -0500 |
---|---|---|
committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2017-02-02 15:21:36 -0500 |
commit | 5a57c1592a34ee6632ca1fb38e076dde381d1ae2 (patch) | |
tree | f06422d16a8b89313202b10f673df70bd72c69fb /extras/contri-add.sh | |
parent | ae47befebeda2de5fd2d706090cbacf4ef60c785 (diff) |
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.
Change-Id: Ibedb8942060bccc96b02272a333c3002c9b77d4c
BUG: 1385758
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
Reviewed-on: https://review.gluster.org/16510
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
Diffstat (limited to 'extras/contri-add.sh')
0 files changed, 0 insertions, 0 deletions