Bug 1396038
| Summary: | refresh-config fails and crashes ganesha when mdcache is enabled on the volume. | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Poornima G <pgurusid> | |
| Component: | md-cache | Assignee: | Poornima G <pgurusid> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | amukherj, anoopcs, bugs, jthottan, kkeithle, madam, mzywusko, ndevos, pgurusid, rhinduja, rhs-bugs, rjoseph, rtalur, sbhaloth, skoduri, sraj, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.10.0 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1384993 | |||
| : | 1396880 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-03 09:07:23 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: | 1384993 | |||
| Bug Blocks: | 1396880 | |||
|
Description
Poornima G
2016-11-17 10:12:01 UTC
REVIEW: http://review.gluster.org/15764 (afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_CHILD_DOWN/UP) posted (#3) for review on master by Poornima G (pgurusid) REVIEW: http://review.gluster.org/15764 (afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_CHILD_DOWN/UP) posted (#4) for review on master by Poornima G (pgurusid) REVIEW: http://review.gluster.org/15764 (afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_CHILD_DOWN/UP) posted (#5) for review on master by Poornima G (pgurusid) REVIEW: http://review.gluster.org/15764 (afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_CHILD_DOWN/UP) posted (#6) for review on master by Poornima G (pgurusid) REVIEW: http://review.gluster.org/15764 (afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_DESCENDENT_DOWN/UP) posted (#7) for review on master by Poornima G (pgurusid) COMMIT: http://review.gluster.org/15764 committed in master by Rajesh Joseph (rjoseph) ------ commit f7ab6c45963fa0da68acedfb14281cd2456abc68 Author: Poornima G <pgurusid> Date: Fri Oct 28 15:27:15 2016 +0530 afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_DESCENDENT_DOWN/UP Currently these are few events related to child_up/down: GF_EVENT_CHILD_UP : Issued when any of the protocol client connects. GF_EVENT_CHILD_MODIFIED : Issued by afr/dht/ec GF_EVENT_CHILD_DOWN : Issued when any of the protocol client disconnects. These events get modified at the dht/afr/ec layers. Here is a brief on the same. DHT: - All the subvolumes reported once, and atleast one child came up, then GF_EVENT_CHILD_UP is issued - connect GF_EVENT_CHILD_UP is issued - disconnect GF_EVENT_CHILD_MODIFIED is issued - All the subvolumes disconnected, GF_EVENT_CHILD_DOWN is issued AFR: - First subvolume came up, then GF_EVENT_CHILD_UP is issued - Subsequent subvolumes coming up, results in GF_EVENT_CHILD_MODIFIED - Any of the subvolumes go down, then GF_EVENT_SOME_CHILD_DOWN is issued - Last up subvolume goes down, then GF_EVENT_CHILD_DOWN is issued Until the patch [1] introduced GF_EVENT_SOME_CHILD_UP, GF_EVENT_CHILD_MODIFIED was issued by afr/dht when any of the subvolumes go up or down. Now with md-cache changes, there is a necessity to differentiate between child up and down. Hence, introducing GF_EVENT_SOME_DESCENDENT_DOWN/UP and getting rid of GF_EVENT_CHILD_MODIFIED. [1] http://review.gluster.org/12573 Change-Id: I704140b6598f7ec705493251d2dbc4191c965a58 BUG: 1396038 Signed-off-by: Poornima G <pgurusid> Reviewed-on: http://review.gluster.org/15764 CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: N Balachandran <nbalacha> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Reviewed-by: Rajesh Joseph <rjoseph> 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.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/ |