Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7CB1B10A53 for ; Thu, 9 Jan 2014 16:49:32 +0000 (UTC) Received: (qmail 1600 invoked by uid 500); 9 Jan 2014 16:48:49 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 1418 invoked by uid 500); 9 Jan 2014 16:48:37 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 1400 invoked by uid 99); 9 Jan 2014 16:48:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 16:48:36 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rickylee0815@gmail.com designates 209.85.212.171 as permitted sender) Received: from [209.85.212.171] (HELO mail-wi0-f171.google.com) (209.85.212.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jan 2014 16:48:29 +0000 Received: by mail-wi0-f171.google.com with SMTP id bz8so7196781wib.4 for ; Thu, 09 Jan 2014 08:48:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=WvGqite8u9DV7Ow9qytdZ6DsNGCDoi161Y3kcMr7QHo=; b=F3lZANdaPeJ6vFSPyHk6GBKhhO9pSa1ulS427ZXcOD4hD07fItvQi7PbT71bah4UIf yraKEm5TGvJ/ON/c3CU3IgEDb0vXbrxlXM51RVX1JU/P3WU3tjWCPGSCTB2wjiKnX/Um 7Bo1lAKIzJFR6yBvestpbvmC82aqtdmIxvsm8TOFP4wO+5t+qjA5saGynwCRnIY5orXU dz0cwAoIcnxFFVzyn3Pjo0EBFjS9dfLQJZyXn6U9Q7ycgAL2kB0He7cH/hwKJyXTkzKC eWfFa2VWWkF2BvdLmAscq2XdmumSzn+2eHie5g/mxyzmB5n6SXPTNPE/ZvEoBsJqtP7k sXZw== MIME-Version: 1.0 X-Received: by 10.180.184.105 with SMTP id et9mr26635918wic.36.1389286088747; Thu, 09 Jan 2014 08:48:08 -0800 (PST) Received: by 10.216.233.193 with HTTP; Thu, 9 Jan 2014 08:48:08 -0800 (PST) Date: Thu, 9 Jan 2014 11:48:08 -0500 Message-ID: Subject: expressing job anti-affinity in Yarn. From: ricky l To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c228a2cfb0dd04ef8c5f90 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c228a2cfb0dd04ef8c5f90 Content-Type: text/plain; charset=ISO-8859-1 Hi all, Is it possible to express the job anti-affinity in the Yarn-based hadoop? I have a job that is very IO-intensive, and I want to spread the tasks across all available machines. In a default Yarn RM scheduler, it seems many tasks are scheduled in one machine while others are idle. thanks. --001a11c228a2cfb0dd04ef8c5f90 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,

Is it possible to express the j= ob anti-affinity in the Yarn-based hadoop? I have a job that is very IO-int= ensive, and I want to spread the tasks across all available machines. In a = default Yarn RM scheduler, it seems many tasks are scheduled in one machine= while others are idle.

thanks.
--001a11c228a2cfb0dd04ef8c5f90--