[ 
https://issues.apache.org/jira/browse/HDDS-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajesh Balamohan updated HDDS-2328:
-----------------------------------
    Description: 
Large-scale listing of directory contents takes a lot longer time and also has 
the potential to run into OOM. I have > 1 million entries in the same level and 
it took lot longer time with {{RemoteIterator}} (didn't complete as it was 
stuck in RDB::seek).

S3A batches it with 5K listing per fetch IIRC.  It would be good to have this 
feature in ozone as well.

  was:
Large-scale listing of directory contents takes a lot longer time and also has 
the potential to run into OOM. I have > 1 million entries in the same level and 
it took lot longer time (didn't complete as it was stuck in RDB::seek).

S3A batches it with 5K listing per fetch IIRC.  It would be good to have this 
feature in ozone as well.


> Support large-scale listing 
> ----------------------------
>
>                 Key: HDDS-2328
>                 URL: https://issues.apache.org/jira/browse/HDDS-2328
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Manager
>            Reporter: Rajesh Balamohan
>            Assignee: Hanisha Koneru
>            Priority: Major
>              Labels: performance
>
> Large-scale listing of directory contents takes a lot longer time and also 
> has the potential to run into OOM. I have > 1 million entries in the same 
> level and it took lot longer time with {{RemoteIterator}} (didn't complete as 
> it was stuck in RDB::seek).
> S3A batches it with 5K listing per fetch IIRC.  It would be good to have this 
> feature in ozone as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to