You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2020/08/25 10:33:00 UTC

[jira] [Resolved] (HADOOP-17074) Optimise s3a Listing to be fully asynchronous.

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

Steve Loughran resolved HADOOP-17074.
-------------------------------------
    Fix Version/s: 3.3.1
       Resolution: Fixed

> Optimise s3a Listing to be fully asynchronous.
> ----------------------------------------------
>
>                 Key: HADOOP-17074
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17074
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Mukund Thakur
>            Assignee: Mukund Thakur
>            Priority: Major
>             Fix For: 3.3.1
>
>
> Listing api returns a Remote iterator. Currently it is blocking in the constructor Listing class. Also it is done in batches, so if a batch is exhausted , the next batch will be fetched from s3 
> thus causing small pauses on the client side every time a batch is fetched. We can add the following optimisations to fix these:
>  * Make the constructor list call to s3 asynchronous.
>  * Fetch the next batch asynchronously while the current batch is getting processed.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org