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 "Daniel Carl Jones (Jira)" <ji...@apache.org> on 2022/06/30 10:52:00 UTC

[jira] [Commented] (HADOOP-18218) Ensure S3A prefetching stream memory consumption scales

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

Daniel Carl Jones commented on HADOOP-18218:
--------------------------------------------

I'll scope this ticket down to focus on memory consumption. HADOOP-18291 highlights that there is no limits or clean-up for the disk cache.

> Ensure S3A prefetching stream memory consumption scales
> -------------------------------------------------------
>
>                 Key: HADOOP-18218
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18218
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.9
>            Reporter: Steve Loughran
>            Priority: Major
>
> A recurrent problem in cloud store IO is running out of memory because blocks are buffered in reads or writes.
> We need to make sure that data/memory is managed in the prefetch code such that it works in processes with many worker threads (hive, spark....) and does not exhaust resources.



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

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