Description of problem: The limitation with <=nfs-ganesha 2.4.x is that ganesha process reads entire directory contents at one go before it starts serving to clients. This results in high latency for directory listing., esp., in case of large directories containing millions of entries, the listing may take few hours to complete making it look like hang. This problem is addressed in 2.5 upstream release with the introduction of readdir-chunk feature. Now the ganesha service shall read directory contents in chunks (chunk size is configurable) and start serving clients sooner thus improving the user experience. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The very basic use case - creates and ls passes on an arbitrated volume. I did not see any hangs , even after 48 hours of I/O and readdirs from v3/v4.0. I am moving the RFE to Verified. Full fledged testing of the feature will be done in Feature Testing/Regression phase.
This should be moved out of 3.4, since dirent chunk is removed.
Hi Rejy/Atin/Ganesha team, I am still not convinced or maybe I am confused. The bug was already in the verified state. What did we verify then? What all issue we see with the current fix? I don't see any bug relevant bug which is blocking this feature? Looks like things are missing on the bug. Why is doc team working on doc text? Can we capture all the details which justify a verified bug being moved out of release? -Bipin Kunal
(In reply to Bipin Kunal from comment #13) > Hi Rejy/Atin/Ganesha team, > > I am still not convinced or maybe I am confused. The bug was already in > the verified state. What did we verify then? > This is an RFE BZ. The move to VERIFIED at this BZ was based on the QE validation of the associated feature being available in a testable form at the Feature Freeze builds, which is a requirement for Feature Freeze criteria Refer to Comment 6 > What all issue we see with the current fix? I don't see any bug relevant > bug which is blocking this feature? Looks like things are missing on the bug. > I will defer to the nfs-ganesha team on this > Why is doc team working on doc text? > I have now asked them not to. > Can we capture all the details which justify a verified bug being moved > out of release? > > -Bipin Kunal
Doc text looks good.
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-2019:3252