hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lqjacklee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15961) S3A committers: make sure there's regular progress() calls
Date Tue, 11 Dec 2018 14:38:00 GMT

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

lqjacklee updated HADOOP-15961:
    Attachment: HADOOP-15961-001.patch

> S3A committers: make sure there's regular progress() calls
> ----------------------------------------------------------
>                 Key: HADOOP-15961
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15961
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Steve Loughran
>            Assignee: lqjacklee
>            Priority: Minor
>         Attachments: HADOOP-15961-001.patch
> MAPREDUCE-7164 highlights how inside job/task commit more context.progress() callbacks
are needed, just for HDFS.
> the S3A committers should be reviewed similarly.
> At a glance:
> StagingCommitter.commitTaskInternal() is at risk if a task write upload enough data to
the localfs that the upload takes longer than the timeout.
> it should call progress it every single file commits, or better: modify {{uploadFileToPendingCommit}}
to take a Progressable for progress callbacks after every part upload.

This message was sent by Atlassian JIRA

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

View raw message