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 94CFADC03 for ; Tue, 21 May 2013 21:58:12 +0000 (UTC) Received: (qmail 82250 invoked by uid 500); 21 May 2013 21:58:08 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 82064 invoked by uid 500); 21 May 2013 21:58:08 -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 82056 invoked by uid 99); 21 May 2013 21:58:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 21:58:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sandy.ryza@cloudera.com designates 209.85.210.48 as permitted sender) Received: from [209.85.210.48] (HELO mail-da0-f48.google.com) (209.85.210.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 21:58:02 +0000 Received: by mail-da0-f48.google.com with SMTP id h32so700283dak.21 for ; Tue, 21 May 2013 14:57:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=r994Ny7+6KRwBd3YwZbjHsDOJNPb6pDFhz7xTYJGtqk=; b=lHs/08Wbi80hpzVD2tYFBYWvrFi5OXswQ3PoJZbL383sdktYgaTwYYspi4WipZS7RU kvIEYqH+/zGcCB+ayWrK6ufCuGt4F9C8x2cWYae7lSzVVfWtjcXnhBXy2OMyrrxEJbtu pIhGWLzdLfzx54O8CeBkwvFEwLRXHhAnadQSibG8Sj04rOSj/lbGNpKCklBF4OG9GqX4 VSEfQsbUef8Lv9P9FzwXoiTALmtFivQ+z53Qr/UJY8HpLAO7T+TS2uZrF0rqBOWvwAwE sObg11NGkGEO6gOb438zaej9uf3FeyDOreutBDfqXZNZwWQnfgLIwkRBVRtI2GwGEa/a eBAw== MIME-Version: 1.0 X-Received: by 10.66.51.102 with SMTP id j6mr5059336pao.210.1369173461163; Tue, 21 May 2013 14:57:41 -0700 (PDT) Received: by 10.70.46.104 with HTTP; Tue, 21 May 2013 14:57:41 -0700 (PDT) In-Reply-To: <3D527B17-E3EC-4988-BEEC-D3CAF8448658@oit.gatech.edu> References: <3D527B17-E3EC-4988-BEEC-D3CAF8448658@oit.gatech.edu> Date: Tue, 21 May 2013 14:57:41 -0700 Message-ID: Subject: Re: Is there a way to limit # of hadoop tasks per user at runtime? From: Sandy Ryza To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=bcaec544f02ec9f31604dd4189e1 X-Gm-Message-State: ALoCoQkivrxEt9EGjfiapbG+SGEngawRaVZaHB5zYIHYBVxy/eO2iDGxm0SMdBecgkfkrkv9NLml X-Virus-Checked: Checked by ClamAV on apache.org --bcaec544f02ec9f31604dd4189e1 Content-Type: text/plain; charset=ISO-8859-1 Hi Mehmet, Are you using MR1 or MR2? The fair scheduler, present in both versions, but configured slightly differently, allows you to limit the number of map and reduce tasks in a queue. The configuration can be updated at runtime by modifying the scheduler's allocations file. It also has a feature that automatically maps jobs to queues based on the user submitted them. Here are links to documentation in MR1 and MR2: http://hadoop.apache.org/docs/stable/fair_scheduler.html http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/FairScheduler.html -Sandy On Tue, May 21, 2013 at 2:43 PM, Mehmet Belgin wrote: > Hi Everyone, > > I was wondering if there is a way for limiting the number of tasks > (map+reduce) *per user* at runtime? Using an environment variable perhaps? > I am asking this from a resource provisioning perspective. I am trying to > come up with a N-token licensing system for multiple users to use our > limited hadoop resources simultaneously. That is, when user A checks out 6 > tokens, he/she can only run 6 hadoop tasks. > > If there is no such thing in hadoop, has anyone tried to integrate hadoop > with torque/moab (or any other RM or scheduler)? Any advice in that > direction will be appreciated :) > > Thanks in advance, > -Mehmet > > > > > > > --bcaec544f02ec9f31604dd4189e1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Mehmet,

Are you using MR1 or M= R2?

The fair scheduler, present in bot= h versions, but configured slightly differently, allows you to limit the nu= mber of map and reduce tasks in a queue. =A0The configuration can be update= d at runtime by modifying the scheduler's allocations file. =A0It also = has a feature that automatically maps jobs to queues based on the user subm= itted them.

Here are links to documentation in MR1 and = MR2:

-Sandy



On Tue, May 21, 2013 at 2:43= PM, Mehmet Belgin <mehmet.belgin@oit.gatech.edu>= wrote:
Hi Every= one,

I was wondering if there is a way for limiting the = number of tasks (map+reduce) *per user* at runtime? Using an environment va= riable perhaps? I am asking this from a resource provisioning perspective. = I am trying to come up with a N-token licensing system for multiple users t= o use our limited hadoop resources simultaneously. That is, when user A che= cks out 6 tokens, =A0he/she can only run 6 hadoop tasks.=A0

If there is no such thing in hadoop, has anyone tried t= o integrate hadoop with torque/moab (or any other RM or scheduler)? Any adv= ice in that direction will be appreciated :)

Thank= s in advance,
-Mehmet







--bcaec544f02ec9f31604dd4189e1--