Bug 1255365
Summary: | Enabling or disabling USS restarts NFS server process on all nodes | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Nag Pavan Chilakam <nchilaka> |
Component: | gluster-nfs | Assignee: | Niels de Vos <ndevos> |
Status: | CLOSED WONTFIX | QA Contact: | storage-qa-internal <storage-qa-internal> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rhgs-3.1 | CC: | nchilaka, skoduri |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-29 11:53:51 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: |
Description
Nag Pavan Chilakam
2015-08-20 11:34:09 UTC
Do you have a tcpdump and/or output from rpcdebug taken on the NFS-client when this happens? I'd also like to know if this only happens with NFS, or also with FUSE mountpoints. Maybe you should test it out by disabling nfs-client caching (using mount option noac). It is by design that gluster-nfs restarts whenever there is change in volfile (which includes enabling uss). Considering that gluster-nfs shall be deprecated sooner, re-designing it doesn't make much sense unless the expected behaviour is not achieved by using alternate solution (which is to use nfs-ganesha). Closing it. I think it should be easily reproducible. I don't have a statedump for this |