Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 86696 invoked from network); 8 Mar 2010 09:46:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Mar 2010 09:46:15 -0000 Received: (qmail 87472 invoked by uid 500); 8 Mar 2010 09:45:52 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 87052 invoked by uid 500); 8 Mar 2010 09:45:52 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 87035 invoked by uid 99); 8 Mar 2010 09:45:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 09:45:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Mar 2010 09:45:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0A6CD234C4B4 for ; Mon, 8 Mar 2010 09:45:28 +0000 (UTC) Message-ID: <742219485.132661268041528041.JavaMail.jira@brutus.apache.org> Date: Mon, 8 Mar 2010 09:45:28 +0000 (UTC) From: "Ravi Gummadi (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-653) distcp can support bandwidth limiting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842604#action_12842604 ] Ravi Gummadi commented on MAPREDUCE-653: ---------------------------------------- Yes. But we need to make sure that a particular distcp-Job's task on a node is not hogging the whole bandwidth available for the node(just to be fair to the other job's tasks running on this node). Also at the time of launching the distcp job, we will not have enough information on the number of tasks of this job that will run paralelly on the cluster at different points of time(because (a) at some point few tasks of this distcp job could be running --- allowing tasks of this distcp job to use high bandwidth per task and (b) at some other time, different number of tasks of this distcp job running --- allowing tasks of this distcp job to use low bandwidth per task). So if sleeping by map task of distcp job looks bad, then distcp needs to find out a way of identifying the number of map tasks to be run(actually, number of map tasks that can run paralelly on the cluster at any point of time ?) so that it can set the bandwidth usage per task properly with lower sleep time. > distcp can support bandwidth limiting > ------------------------------------- > > Key: MAPREDUCE-653 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-653 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: distcp > Reporter: Ravi Gummadi > Assignee: Ravi Gummadi > Attachments: d_bw.patch, d_bw.v1.patch, d_bw.v2.patch > > > distcp should support an option for user to specify the bandwidth limit for the distcp job. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.