glusterd: don't queue attach reqs before connecting

This was causing USS tests to fail.  The underlying problem here is
that if we try to queue the attach request too soon after starting a
brick process then the socket code will get an error trying to write
to the still-unconnected socket.  Its response is to shut down the
socket, which causes the queued attach requests to be force-unwound.
There's nothing to retry them, so they effectively never happen and
those bricks (second and succeeding for a snapshot) never become
available.

We *do* have a retry loop for attach requests, but currently break out
as soon as a request is queued - not actually sent.  The fix is to
modify that loop so it will wait some more if the rpc connection isn't
even complete yet.  Now we break out only when we have a completed
connection *and* a queued request.

Backport of:
> 53e2c875cf97df8337f7ddb5124df2fc6dd37bca
> BUG: 1430148
> Reviewed-on: https://review.gluster.org/16868

Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
BUG: 1431176
Change-Id: Ib6be13646f1fa9072b4a944ab5f13e1b29084841
Reviewed-on: https://review.gluster.org/16887
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>

0 files changed, 0 insertions, 0 deletions