Bug 1475699
| Summary: | [RFE]nfs-ganesha: Read directory contents in chunks | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Soumya Koduri <skoduri> | |
| Component: | nfs-ganesha | Assignee: | Frank Filz <ffilz> | |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.2 | CC: | amukherj, asriram, bkunal, dang, ffilz, jthottan, kkeithle, pasik, psony, rcyriac, rhinduja, rhs-bugs, sanandpa, sheggodu, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | FutureFeature | |
| Target Release: | RHGS 3.5.0 | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | nfs-ganesha-2.7.3-3 | Doc Type: | Enhancement | |
| Doc Text: |
Directory contents are now read in configurable chunks so that very large directory listings can start to be served faster, instead of needing to wait for the whole directory to be read before serving to clients.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1695078 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-30 12:15:39 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: | 1472942, 1730686, 1732671 | |||
| Bug Blocks: | 1382343, 1403648, 1403757, 1415608, 1695078, 1696803 | |||
|
Description
Soumya Koduri
2017-07-27 07:59:30 UTC
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 |