Bug 1419429
| Summary: | [Doc] : mdcache on Ganesha needs to be documented | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> |
| Component: | doc-Administration_Guide | Assignee: | storage-doc |
| doc-Administration_Guide sub component: | Default | QA Contact: | Prasanth <pprakash> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | asriram, bturner, jthottan, kkeithle, pasik, pprakash, rhs-bugs, skoduri, storage-doc |
| Version: | rhgs-3.2 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-25 16:26:05 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
Ambarish
2017-02-06 06:43:04 UTC
I assume this attribute belongs to Ganesha Attr_Expiration_Time=600. First of all I don't recommend enabling md-cache in Ganesha because Ganesha maintains its own cache. Secondly is there a need for Attr_Expiration_Time to be in sync with md-cache-timeout? or it just a coincidence that these values are same? (In reply to rjoseph from comment #2) > I assume this attribute belongs to Ganesha Attr_Expiration_Time=600. First > of all I don't recommend enabling md-cache in Ganesha because Ganesha > maintains its own cache. Secondly is there a need for Attr_Expiration_Time > to be in sync with md-cache-timeout? or it just a coincidence that these > values are same? Hi Rajesh, Yes. That option value is for nfs-ganesha process and by default the value is 60sec. We have been told that there are no protocol specific recommendations done for md-cache settings unless any issues are found wrt functionality or performance. That would mean, admin/customer could try these options even on nfs-ganesha cluster setup. In order to make maximum use of caching (if enabled), we recommend to increase the cache-timeout value in ganesha layer as well to 600sec to match with md-cache timeout value.
> Yes. That option value is for nfs-ganesha process and by default the value
> is 60sec. We have been told that there are no protocol specific
> recommendations done for md-cache settings unless any issues are found wrt
> functionality or performance. That would mean, admin/customer could try
> these options even on nfs-ganesha cluster setup. In order to make maximum
> use of caching (if enabled), we recommend to increase the cache-timeout
> value in ganesha layer as well to 600sec to match with md-cache timeout
> value.
Yes, I know for testing md-cache it was told that every module and protocol should test it by enabling it. But practically speaking having two sets of cache on the same side will not benefit the user. In fact the memory consumption will go high without much gain. In your testing have seen any gain in any workload by enabling both ganesha and gluster md-cache? If not then isn't it prudent to recommend only one set of cache for Ganesha?
If your team decides to go ahead with both types of cache then is it OK to add just the Ganesha specific option in a note instead of creating an entirely new section?
|