Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 6F9BE104A6 for ; Mon, 28 Apr 2014 19:57:55 +0000 (UTC) Received: (qmail 87791 invoked by uid 500); 28 Apr 2014 19:57:47 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 87627 invoked by uid 500); 28 Apr 2014 19:57: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 87619 invoked by uid 99); 28 Apr 2014 19:57:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Apr 2014 19:57:46 +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 (athena.apache.org: domain of bobyangbo@gmail.com designates 209.85.212.179 as permitted sender) Received: from [209.85.212.179] (HELO mail-wi0-f179.google.com) (209.85.212.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Apr 2014 19:57:41 +0000 Received: by mail-wi0-f179.google.com with SMTP id z2so6288240wiv.12 for ; Mon, 28 Apr 2014 12:57:20 -0700 (PDT) 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=WZMfO67/lBtvLf6Z1Nt+7N9moOH8AbwiOR+xl982vx0=; b=sK9VqS+Gu4hcbHFqcNKqsXXIm9TC3RMdnfy3JfJ8wOsPJyQ6GFZt1qef0WJNVGT7x2 55/HDJ35K1D850CD60aD/QjhwiZh4XpF+RQuwG0PiJY6xZTeapAZayrXURx32yKU/w8H SWI65IWaar/2fmL6PecHQaBtyfK21Hgz4ZFOgu1GCiIIWds9+z+PUHNfbVJvDeNE6YO1 Ju01YHKsRmrSQr6FUXWBwK6aUGz4ixsEExMecs2KP35n4Ff51fQmk6kROlRw90pVSQqB 7mFir+Jn9KHe3opQaiZIp99PsHTHpBFzpb/yV6QUtpVH6FHXz4hH3iWaD9k8rpAiJVLI r67A== MIME-Version: 1.0 X-Received: by 10.194.204.199 with SMTP id la7mr20892863wjc.4.1398715040309; Mon, 28 Apr 2014 12:57:20 -0700 (PDT) Received: by 10.217.66.70 with HTTP; Mon, 28 Apr 2014 12:57:20 -0700 (PDT) Date: Mon, 28 Apr 2014 12:57:20 -0700 Message-ID: Subject: Running YARN in-process Application Master? From: bo yang To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bae478e1ea83d04f81fb925 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bae478e1ea83d04f81fb925 Content-Type: text/plain; charset=UTF-8 Hi All, I just joined this group, and not sure whether this question was discussed before. Is it possible to run Application Master within the same process as Node Manager? If not, any plan to support it future? I am asking this because we might want to use YARN as a job dispatching system. We have our own heavy-weight service which is not practical to be launched as a new process for each new job. A possible thing we can do is to use YARN to launch a new dummy Application Master process which will dispatch the job to our service. But that new dummy process is a little waste. So if YARN supports in-process Application Master, that will be great. Thanks, Bo --047d7bae478e1ea83d04f81fb925 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi All,

I just joined this g= roup, and not sure whether this question was discussed before.
Is it possible to run Application Master within the same proce= ss as Node Manager? If not, any plan to support it future?

I am asking this because we might want to use YARN as a= job dispatching system. We have our own heavy-weight service which is not = practical to be=C2=A0launched as=C2=A0a new process for each new job. A pos= sible thing we can do is to use YARN to launch a new dummy Application Mast= er process which will dispatch the job to our service. But that new dummy p= rocess is a little waste. So if YARN supports in-process Application Master= , that will be great.

Thanks,
Bo

--047d7bae478e1ea83d04f81fb925--