Return-Path: 
 <user-return-11943-apmail-hadoop-hdfs-user-archive=hadoop.apache.org@hadoop.apache.org>
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 DF4B410081
	for <apmail-hadoop-hdfs-user-archive@minotaur.apache.org>;
 Thu, 21 Nov 2013 15:52:46 +0000 (UTC)
Received: (qmail 69388 invoked by uid 500); 21 Nov 2013 15:52:37 -0000
Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org
Received: (qmail 68978 invoked by uid 500); 21 Nov 2013 15:52:29 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 68970 invoked by uid 99); 21 Nov 2013 15:52:28 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 15:52:28 +0000
X-ASF-Spam-Status: No, hits=1.7 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of rickylee0815@gmail.com
 designates 209.85.212.176 as permitted sender)
Received: from [209.85.212.176] (HELO mail-wi0-f176.google.com)
 (209.85.212.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 15:52:22 +0000
Received: by mail-wi0-f176.google.com with SMTP id f4so8841981wiw.9
        for <user@hadoop.apache.org>; Thu, 21 Nov 2013 07:52:02 -0800 (PST)
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=NRrNASCyvU++UKATO4tKgJR8JYWWAh1aj2kEd+5TwlI=;
        b=qF77Lk+wBHAGiwbu1nEW84xB3ZhK5kZTW0sZQKusrq1qpZL22ZL3Q179VAHhUyfX7t
         QDp2HeoMUVpEBBNkz4phzEvj5d5+HhD+QAAkxDpDH8VPM4+UtHPG7G3F37Fzzt0DCMoI
         VD1SS5hn1mIm1acGdd5o7jjypXfDj/LSgpbsKF3PdD10ANsG7dM5RC60kaXJzkdbJMPQ
         A6cLBNkoAy32alTV/6Sx857HRN6+1bCQC54Jgvp2n9t4m2j9A82ASrSQSSSKKvUT9iMX
         HNTTqNFPZv2PAq7LvrDkMoYzBlxZWQLB5zGirHCnMFTsRe20tHKENCgIGLhQzRldeQtH
         8PDw==
MIME-Version: 1.0
X-Received: by 10.180.208.4 with SMTP id ma4mr6281674wic.43.1385049121696;
 Thu, 21 Nov 2013 07:52:01 -0800 (PST)
Received: by 10.216.236.65 with HTTP; Thu, 21 Nov 2013 07:52:01 -0800 (PST)
Date: Thu, 21 Nov 2013 10:52:01 -0500
Message-ID: 
 <CADoVA9oWsweVuYQyVJsUrskqohh617DkFz+ub=C-C8A4rwdTMw@mail.gmail.com>
Subject: In YARN, how does a task tracker knows the address of a job tracker?
From: ricky l <rickylee0815@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001a11c387e0e52f2704ebb1e052
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c387e0e52f2704ebb1e052
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I have a question of how a task tracker identifies job tracker address when
I submit MR job through YARN. As far as I know, both job tracker and task
trackers are launched through application master and I am curious about the
details about job and task tracker launch sequence.

thanks.

--001a11c387e0e52f2704ebb1e052
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>I have a question of how a task=
 tracker identifies job tracker address when I submit MR job through YARN. =
As far as I know, both job tracker and task trackers are launched through a=
pplication master and I am curious about the details about job and task tra=
cker launch sequence.</div>
<div><br></div><div>thanks.=A0</div></div>

--001a11c387e0e52f2704ebb1e052--