Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <13212869.1193168690664.JavaMail.jira@brutus>
Date: Tue, 23 Oct 2007 12:44:50 -0700 (PDT)
From: "Chris Douglas (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-2048) DISTCP mapper should report progress
 more often
In-Reply-To: <22841690.1192232150855.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Douglas updated HADOOP-2048:
----------------------------------

    Attachment:     (was: 2048.patch)

> 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-3.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.