From yarn-dev-return-945-apmail-hadoop-yarn-dev-archive=hadoop.apache.org@hadoop.apache.org Tue Feb 19 22:38:39 2013 Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F585D0E8 for ; Tue, 19 Feb 2013 22:38:39 +0000 (UTC) Received: (qmail 94186 invoked by uid 500); 19 Feb 2013 22:38:39 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 94104 invoked by uid 500); 19 Feb 2013 22:38:39 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 94091 invoked by uid 99); 19 Feb 2013 22:38:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 22:38:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.223.177 as permitted sender) Received: from [209.85.223.177] (HELO mail-ie0-f177.google.com) (209.85.223.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 22:38:33 +0000 Received: by mail-ie0-f177.google.com with SMTP id 16so9261994iea.36 for ; Tue, 19 Feb 2013 14:38:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=NbF+ei0oNv73GT2uXGgSN9XHianaoMYmO8Nxu0qrR9U=; b=Ugej0GX1WWz55Xr8RxAuTnZxqO11riPAUksXnAc0jfABZrODA1/dEf6IOxNeMKhU1E 1W6mdt3zhfWBIRKEFfio26x7QlewwibIvWhhD4cdADHgAJMFQn+1HSIXhd14YSUpozyr +ofoCOUEB+hxZvYSXifsAswtAomoIRaC0t52ZatpMC2K40OJti7I+uLcEtCLI9Vh1lBZ wJw1MpC/lyK0UkV52sINmdRyzwvFAXLRzNm+5OcHBoZQU48ZQgR2CnnWZ8TvnAWlTclN pT+O1FaS6BIMXMnbKWyyVFuG1/q8owTGjNNgH/5nMBtmYk3gmESwD4idFivQYW9hYfw8 NrCQ== X-Received: by 10.50.191.228 with SMTP id hb4mr9130244igc.37.1361313493161; Tue, 19 Feb 2013 14:38:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.104.229 with HTTP; Tue, 19 Feb 2013 14:37:53 -0800 (PST) In-Reply-To: References: <563EBA97-14AB-43EE-A373-483AE986CA8C@hortonworks.com> From: Harsh J Date: Wed, 20 Feb 2013 04:07:53 +0530 Message-ID: Subject: Re: multiple resource scheduler questions To: yarn-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnrZxPJFBQ5q6XCBNksB20iv8C8+Vpyume96PaRkoFESEcrmPydYg3YvwvN/AjVeuLTv2JM X-Virus-Checked: Checked by ClamAV on apache.org Is https://issues.apache.org/jira/browse/YARN-291 what you were referring to Arun? On Tue, Feb 19, 2013 at 4:39 AM, Azuryy Yu wrote: > Thanks Arun. > On Feb 18, 2013 11:56 PM, "Arun C Murthy" wrote: > >> >> On Feb 18, 2013, at 1:26 AM, Azuryy Yu wrote: >> >> > Hi >> > There are two configure items: >> > >> > yarn.nodemanager.resource.memory-mb, default 8GB >> > yarn.nodemanager.resource.cpu-cores, default 8 >> > >> > >> > If I have some nodes with different hardware configuration(maybe pool >> > hardware or advanced hardware), then I have to do some special >> > configuration for these nodes? >> >> Yes, for now just configure yarn-site.xml individually on the nodes. >> >> > If node manager can recognize system available resources, that would be >> > better. >> >> Agreed, there is a open-jira for this ask - can't seem to find it ATM. >> >> Arun >> >> -- >> Arun C. Murthy >> Hortonworks Inc. >> http://hortonworks.com/ >> >> >> -- Harsh J