Bug 1461507
| Summary: | [Ganesha] : Ganesha logs flooded with "unable to find reclaimable dupreq LRU entry" messages | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> |
| Component: | nfs-ganesha | Assignee: | Kaleb KEITHLEY <kkeithle> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, bturner, chpai, dang, ffilz, info, jthottan, kkeithle, mbenjamin, msaini, pmulay, rhinduja, rhs-bugs, sheggodu, skoduri, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | 3.3.0-defer | ||
| Fixed In Version: | nfs-ganesha-2.5.4-1 | Doc Type: | Known Issue |
| Doc Text: |
When duplicate request cache (DRC) entries maintained by NFS-Ganesha server reaches the high watermark limit, the server tries to reclaim old entries which may still be in use. As a result, every time the server cannot reclaim an entry, it logs a warning. This may flood the log file at times if there are too many requests being processed.
Workaround: Increase the DRC limit by executing the following steps:
1) Edit the /run/gluster/shared_storage/nfs-ganesha/ganesha.conf file and add the following parameters in NFS_Core_Param block:
NFS_Core_Param
{
DRC_TCP_Hiwat = 1024; #default is 256
}
2) Restart the NFS-Ganesha process on all the nodes in the NFS-Ganesha cluster using the following command:
# systemctl restart nfs-ganesha
This decreases the chances of these warnings filling up the logs.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-04 06:53:35 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: | |||
| Bug Blocks: | 1417153, 1503135 | ||
|
Description
Ambarish
2017-06-14 15:55:46 UTC
A simple code fix to this could be to just change the log level of that message. (In reply to Frank Filz from comment #9) > A simple code fix to this could be to just change the log level of that > message. But then will you not actually be suppressing the log for a genuine failure as well? (In reply to Atin Mukherjee from comment #10) > (In reply to Frank Filz from comment #9) > > A simple code fix to this could be to just change the log level of that > > message. > > But then will you not actually be suppressing the log for a genuine failure > as well? Hmm, considering what Matt said, it is actually warning about something that is really happening, so I guess the config fix is the best workaround, so never mind about my idea for a quick code fix... You can also turn logging down for the DUPREQ component like this:
LOG {
Components {
DUPREQ = CRIT;
}
}
(That log line is at the WARN level, so CRIT or lower will disable that warning).
POST with rebase to nfs-ganesha-2.5.x Is this intended to be a doctext for 3.4? Because 3.4 is base on 2.5, which has this fixed, and doesn't even have that log message in it anymore. This should just be closed fixed with no doctext in 3.4. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2610 |