Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B465110FA9 for ; Tue, 19 Nov 2013 22:02:05 +0000 (UTC) Received: (qmail 80197 invoked by uid 500); 19 Nov 2013 22:02:00 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 79892 invoked by uid 500); 19 Nov 2013 22:01:59 -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 79881 invoked by uid 99); 19 Nov 2013 22:01:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Nov 2013 22:01:59 +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 ojoshi@hortonworks.com designates 209.85.215.49 as permitted sender) Received: from [209.85.215.49] (HELO mail-la0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Nov 2013 22:01:53 +0000 Received: by mail-la0-f49.google.com with SMTP id er20so6466776lab.8 for ; Tue, 19 Nov 2013 14:01:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=qS2Erp6oh5o6SHCM1a9Lx8Fr9SAVaaaxsBLnxsBULGo=; b=MXnzuOa4xvQaJTE5A+0gWX/qzc3ahHQ34ncTAhLUXwRa2EH36rSxi1k3eBI52aUsSc MEeqdt2lP3ULrxq24cOoMOqJktDoVubC7Gacp57Eq9wvDItABDwNK1zVAje5WVJDfNGG rb+4HKYq/pLfVsDMoJKIUniV+PJNoQNU4Dcu4WQ4OsoCFi0QiLa9yKrengGUHCdXn93S wDjrhZqe7XGXL9c5F/Ome3KQE9pmrwsMnaF45eT0ohBlXSasRJq9mOtYbO0bkUIKBFL0 WB66WxL0QJCs6unXMsyrwLe5555Q2uzV7uEhbR2qY0QafRwVmviEYqs6MI7v3RcQxXvN BOzw== X-Gm-Message-State: ALoCoQljV4I/+NM5kg63FZdnRposxKSslaFlqh0Jd4mAFLhyZ4E9vzwwNvqj4NDG8pKJ3oa2791XWtUGEx0/Ev8oPz1WUqUYESeUTylLFzQjdeZxgyKnIBs= MIME-Version: 1.0 X-Received: by 10.152.116.7 with SMTP id js7mr20511374lab.11.1384898492971; Tue, 19 Nov 2013 14:01:32 -0800 (PST) Received: by 10.112.182.97 with HTTP; Tue, 19 Nov 2013 14:01:32 -0800 (PST) In-Reply-To: References: Date: Tue, 19 Nov 2013 14:01:32 -0800 Message-ID: Subject: Re: Limit on total jobs running using fair scheduler From: Omkar Joshi To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c2672ab94db704eb8eced1 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2672ab94db704eb8eced1 Content-Type: text/plain; charset=US-ASCII Not sure about the fair scheduler but in capacity scheduler you can achieve this by controlling number of jobs/applications per queue. Thanks, Omkar Joshi *Hortonworks Inc.* On Tue, Nov 19, 2013 at 3:26 AM, Ivan Tretyakov wrote: > Hello! > > We are using CDH 4.1.1 (Version: 2.0.0-mr1-cdh4.1.1) and fair-scheduler. > We need to limit total number of jobs which can run at the same time on > cluster. > I can see maxRunningJobs options but it sets limit for pool or user. > We wouldn't like to limit each pool or user we just need to set limit on > total number of jobs running. > > Is it possible to do it using fair scheduler? > Can capacity scheduler help here? > Maybe there are other options to achieve the goal? > > Thanks in advance! > > -- > Best Regards > Ivan Tretyakov > > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --001a11c2672ab94db704eb8eced1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Not sure about the fair scheduler but in capacity schedule= r you can achieve this by controlling number of jobs/applications per queue= .

Thanks,
Omkar Joshi


On Tue, Nov 19, 2013 at 3:26 AM, Ivan Tr= etyakov <itretyakov@griddynamics.com> wrote:
Hello!

We are using CDH 4.1.1 (Version:= 2.0.0-mr1-cdh4.1.1) and fair-scheduler.
We need to limit total n= umber of jobs which can run at the same time on cluster.
I can se= e=A0maxRunningJobs options but it sets limit for pool or user.
We wouldn't like to limit each pool or user we just need to set li= mit on total number of jobs running.

Is it possibl= e to do it using fair scheduler?
Can capacity scheduler help here= ?=A0
Maybe there are other options to achieve the goal?

Thanks in advance!

--
Best Regards
I= van Tretyakov



CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u. --001a11c2672ab94db704eb8eced1--