Bug 1430042
Summary: | Transport endpoint not connected error seen on client when glusterd is restarted | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Jeff Darcy <jdarcy> |
Component: | rpc | Assignee: | Jeff Darcy <jeff> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | amukherj, bugs, jdarcy, kramdoss |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | brick-multiplexing-testing | ||
Fixed In Version: | glusterfs-3.11.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1422781 | Environment: | |
Last Closed: | 2017-05-30 18:46:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1422781 | ||
Bug Blocks: |
Description
Jeff Darcy
2017-03-07 18:01:02 UTC
REVIEW: https://review.gluster.org/16866 (glusterfsd: don't quit (in client) on connection failure) posted (#2) for review on master by Jeff Darcy (jdarcy) COMMIT: https://review.gluster.org/16866 committed in master by Jeff Darcy (jdarcy) ------ commit eb038c19e2c799e35e72eeb500dfb81efc5567e2 Author: Jeff Darcy <jdarcy> Date: Tue Mar 7 11:53:04 2017 -0500 glusterfsd: don't quit (in client) on connection failure Change-Id: I32be91e9db361a45454d6340a4c4ac2d0d7efffc BUG: 1430042 Signed-off-by: Jeff Darcy <jdarcy> Reviewed-on: https://review.gluster.org/16866 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Prashanth Pai <ppai> REVIEW: https://review.gluster.org/16665 (tests: add test for restarting glusterd with I/O ongoing) posted (#2) for review on master by Jeff Darcy (jdarcy) This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report. glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/ |