Bug 763941 (GLUSTER-2209)
Summary: | [3.1.1-GA] gNFS goes into an unusable state if dns-lookups fail | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Harshavardhana <fharshav> |
Component: | nfs | Assignee: | Shehjar Tikoo <shehjart> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.1.1 | CC: | cww, gluster-bugs, vijay |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | RTP | Mount Type: | nfs |
Documentation: | DP | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harshavardhana
2010-12-10 19:46:23 UTC
Yeah, there is already a bug filed for it. Will look into it again. harsha, this is where we discussed this before and the reasoning in the last comment still applies. http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1390#c11 I still hold that view that it is simpler to restart nfs than make the large code change that is needed to fix the problem. What do you think? (In reply to comment #2) > harsha, this is where we discussed this before and the reasoning in the last > comment still applies. > > http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1390#c11 > > I still hold that view that it is simpler to restart nfs than make the large > code change that is needed to fix the problem. What do you think? I don't really understand the idea of NFS doing a reverse lookup and failing all the time even after the issue is fixed. Problem is major when you have to restart the service, the perpetuation of the issue even after DNS fixed is my concern. If this is how its going to be, we need to clearly mention in our documentation and what are the expected results on client side when a live i/o is going on. (In reply to comment #3) > (In reply to comment #2) > > harsha, this is where we discussed this before and the reasoning in the last > > comment still applies. > > > > http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1390#c11 > > > > I still hold that view that it is simpler to restart nfs than make the large > > code change that is needed to fix the problem. What do you think? > > I don't really understand the idea of NFS doing a reverse lookup and failing > all the time even after the issue is fixed. Problem is major when you have to > restart the service, the perpetuation of the issue even after DNS fixed is my > concern. > The issue is not fixed. Just dont think it should be fixed. > If this is how its going to be, we need to clearly mention in our documentation > and what are the expected results on client side when a live i/o is going on. Where would you like this documented? Is the gluster nfs FAQ page accessible enough by you? > The issue is not fixed. Just dont think it should be fixed. > Ok > > Where would you like this documented? Is the gluster nfs FAQ page accessible > enough by you? Good enough, for support team. It would be easy for them also. Will be documented by Divya. |