[ 
https://issues.apache.org/jira/browse/HDDS-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622351#comment-17622351
 ] 

Devesh Kumar Singh commented on HDDS-7360:
------------------------------------------

For scenario 1:

 

his 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 begining. I 
have fixed the issue of hung when pageSize is set as 1, after discussing with 
[~sammichen]  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, normalize to 2 , rest all as 
per actual configuration.. because once startKey reaches leaf level, then it 
returns itself which is expected beahvior

> Investigate "TestRootedOzoneFileSystem" test cases
> --------------------------------------------------
>
>                 Key: HDDS-7360
>                 URL: https://issues.apache.org/jira/browse/HDDS-7360
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Devesh Kumar Singh
>            Assignee: Devesh Kumar Singh
>            Priority: Minor
>
> 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 I give value at client less than equal to 1, it hung.
> 2. If I 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to