devmadhuu opened a new pull request, #3899: URL: https://github.com/apache/ozone/pull/3899
## What changes were proposed in this pull request? Investigate "TestRootedOzoneFileSystem" test cases in below scenarios for setting value of property "ozone.fs.listing.page.size" as per below scenarios and verify all test cases running fine and pass. 1. If give value at client less than equal to 1, it hung. 2. If give value more than 1 upto 3, then it doesn't hung any of the test case of TestRootedOzone file, but "listStatusCheckHelper" method makes assertion fail for 2-3 test cases. 3. If give value more than 3, all test cases passed. https://issues.apache.org/jira/browse/HDDS-7360 Investigate "TestRootedOzoneFileSystem" test cases ## How was this patch tested? Ran manually "TestRootedOzoneFileSystem" test cases with below 3 scenarios mentioned in JIRA. First scenario explanation is given below: Scenario1: listingPageSize is not for the listing of overall complete list shown on CLI, this parameter is used for retrieving the listingPageSize number of items from keyTable for a given startKey, so this is the behavior from beginning. I have fixed the issue of hung when pageSize is set as 1, after discussing with @ChenSammi and other members... that startKey behavior is something which we cannot change as of now , so better we should limit this limitPageSize always be greater than 1, so when client configures as 1, normalise to 2 , rest all as per actual configuration.. because once startKey reaches leaf level, then it returns itself which is expected behavior. Scenario2: Assertion is happening on below 2 values: - One with recursive call of listStatus function and passing "/" as startPath which is beginning of volumes and then buckets, keys... - Another value assertion on non-recursive call of listStatus but trying to implement recursive behavior in test code Asserting these expected and actual values seems will fail as non-recursive listStatus implementation on client side works as expected based on startPath and dependent on number of volumes which test code is creating, So here test code is creating 3 volumes , so that is the reason with listing page size up to 3 value, assertion fails. Test code should not assert on these 2 values if listing page size goes less than number of volumes user is having. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
