Bug 1233151
| Summary: | rm command fails with "Transport end point not connected" during add brick | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sakshi <sabansal> |
| Component: | distribute | Assignee: | Sakshi <sabansal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | amukherj, bugs, dlambrig, nbalacha, rhs-bugs, shmohan, smohan, storage-qa-internal, vbellur |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | dht-add-brick | ||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 994405 | Environment: | |
| Last Closed: | 2016-06-16 13:13:39 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: | 994405, 1265890, 1273354 | ||
| Bug Blocks: | 1225330, 1229270, 1229271, 1235202 | ||
|
Description
Sakshi
2015-06-18 10:48:25 UTC
The main issue is that, irrespective of whether the newly added brick received a port or not the volume file change happens. So consider a scenario where the newly added brick requested for a new port but has not received a port, however volume file change happens. Hence fops are now sent to the newly added brick as well. The newly added brick still does not have a port yet hence the fop fails on that brick with "Transpor endpoint not connected". Also instead of glusterd creating and notifying the volfile immediately, it can notify the client once the brick is added. The fix would be to notify volume file change only after a new brick is added and has gets a port. REVIEW: http://review.gluster.org/11342 (glusterfsd: newly added brick receives fops only after it is started) posted (#2) for review on master by Sakshi Bansal REVIEW: http://review.gluster.org/11342 (glusterfsd: newly added brick receives fops only after it is started) posted (#3) for review on master by Dan Lambright (dlambrig) REVIEW: http://review.gluster.org/11342 (glusterfsd: newly added brick receives fops only after it is started) posted (#4) for review on master by Dan Lambright (dlambrig) REVIEW: http://review.gluster.org/11342 (glusterfsd: newly added brick receives fops only after it is started) posted (#5) for review on master by Dan Lambright (dlambrig) REVIEW: http://review.gluster.org/11342 (glusterfsd: newly added brick receives fops only after it is started) posted (#6) for review on master by Vijay Bellur (vbellur) REVIEW: http://review.gluster.org/11342 (glusterfsd : newly added brick receives fops only after it is started) posted (#7) for review on master by Sakshi Bansal (sabansal) REVIEW: http://review.gluster.org/11342 (glusterfsd : newly added brick receives fops only after it is started) posted (#8) for review on master by Dan Lambright (dlambrig) 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |