Bug 1428070 - protocol/client: Fix race in brick reconnection
Summary: protocol/client: Fix race in brick reconnection
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 19:05 UTC by Vijay Bellur
Modified: 2018-10-08 17:30 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.12.13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-08 17:30:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Vijay Bellur 2017-03-01 19:05:49 UTC
protocol/client: Fix race in brick reconnection

Summary:
- A race condition exists when reconnecting to a brick after connection
  has been lost; it is possible for the client translator to believe the
  connection is down while the socket layer believes the connection is up.
  This situation is permanent and eventually leads to loss of quorum
  and EROFS errors.

- This is a cherry-pick of D3490020 to 3.8

Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

Change-Id: Ida7afbafd3dceadf9ca7ea8b350aa88db382dd88
Reviewed-on: http://review.gluster.org/16174
Reviewed-by: Kevin Vigor <kvigor@fb.com>
Tested-by: Shreyas Siravara <sshreyas@fb.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>


Note You need to log in before you can comment on or make changes to this bug.