hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2048) DISTCP mapper should report progress more often
Date Fri, 19 Oct 2007 22:50:50 GMT

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

Owen O'Malley updated HADOOP-2048:
----------------------------------

    Fix Version/s: 0.15.0
         Priority: Blocker  (was: Major)
      Description: 
When I ran DISTCP to copy files from one dfs to another, I noticed that some mappers got killed
due to failing to report status for 606 seconds. 
I noticed that the mappers try to make a progress report for every 32MB copied. A better way
to ensure progress is to use a time interval since last report.




  was:

When I ran DISTCP to copy files from one dfs to another, I noticed that some mappers got killed
due to failing to report status for 606 seconds. 
I noticed that the mappers try to make a progress report for every 32MB copied. A better way
to ensure progress is to use a time interval since last report.





This is a very important patch for distcp to ensure that the copy worked correctly and should
be part of 15.

> DISTCP mapper should report progress more often
> -----------------------------------------------
>
>                 Key: HADOOP-2048
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2048
>             Project: Hadoop
>          Issue Type: Bug
>            Reporter: Runping Qi
>            Assignee: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2048-2.patch, 2048-3.patch, 2048.patch
>
>
> When I ran DISTCP to copy files from one dfs to another, I noticed that some mappers
got killed due to failing to report status for 606 seconds. 
> I noticed that the mappers try to make a progress report for every 32MB copied. A better
way to ensure progress is to use a time interval since last report.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message