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 B3F3D10CAA for ; Wed, 30 Oct 2013 02:32:59 +0000 (UTC) Received: (qmail 50582 invoked by uid 500); 30 Oct 2013 02:32:50 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 50446 invoked by uid 500); 30 Oct 2013 02:32:47 -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 50439 invoked by uid 99); 30 Oct 2013 02:32:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Oct 2013 02:32:46 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of raymond.liu@intel.com designates 134.134.136.24 as permitted sender) Received: from [134.134.136.24] (HELO mga09.intel.com) (134.134.136.24) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Oct 2013 02:32:42 +0000 Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 29 Oct 2013 19:28:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.93,535,1378882800"; d="scan'208";a="426809433" Received: from fmsmsx104.amr.corp.intel.com ([10.19.9.35]) by orsmga002.jf.intel.com with ESMTP; 29 Oct 2013 19:32:19 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX104.amr.corp.intel.com (10.19.9.35) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 29 Oct 2013 19:32:07 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.240]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.49]) with mapi id 14.03.0123.003; Wed, 30 Oct 2013 10:31:37 +0800 From: "Liu, Raymond" To: "user@hadoop.apache.org" Subject: RE: Yarn 2.2 docs or examples? Thread-Topic: Yarn 2.2 docs or examples? Thread-Index: Ac7VELJNY5fE8FccT1OzDvTDBOancf//f9gA//9xeaA= Date: Wed, 30 Oct 2013 02:31:36 +0000 Message-ID: <391D65D0EBFC9B4B95E117F72A360F1A010CB274@SHSMSX101.ccr.corp.intel.com> References: <391D65D0EBFC9B4B95E117F72A360F1A010CB22F@SHSMSX101.ccr.corp.intel.com> In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Thanks Jian, Though this simple example not cover all my problems, but at least give me = a big picture on what's the minimum code needed ;)=20 Best Regards, Raymond Liu From: Jian He [mailto:jhe@hortonworks.com]=20 Sent: Wednesday, October 30, 2013 10:00 AM To: user@hadoop.apache.org Subject: Re: Yarn 2.2 docs or examples? Hi Raymond You may get some help from=A0https://github.com/hortonworks/simple-yarn-app= . It's a simple app written with YARN-beta API Thanks, Jian On Tue, Oct 29, 2013 at 6:46 PM, Liu, Raymond wrote= : Hi =A0 =A0 =A0 =A0 I am playing with YARN 2.2, try to porting some code from p= re-beta API on to the stable API. While both the wiki doc and API doc for 2= .2.0 seems still stick with the old API. Though I could find some help from= http://hortonworks.com/blog/stabilizing-yarn-apis-for-apache-hadoop-2-beta= -and-beyond/ I still find it pretty hard figure out what's the correct way = to use 2.2 API. Since a lot of API changes and some NM / AMRM client API ad= ded. I have to dig into the commit log or try to find some clue from the un= it test case. =A0 =A0 =A0 =A0 So is there any docs or example I can take a look for refer= ence? Best Regards, Raymond Liu 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, pr= ivileged and exempt from disclosure under applicable law. If the reader of = this message is not the intended recipient, you are hereby notified that an= y printing, copying, dissemination, distribution, disclosure or forwarding = of this communication is strictly prohibited. If you have received this com= munication in error, please contact the sender immediately and delete it fr= om your system. Thank You.