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 8CB7F1186E for ; Sat, 7 Jun 2014 14:12:33 +0000 (UTC) Received: (qmail 99353 invoked by uid 500); 7 Jun 2014 14:12:28 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 99230 invoked by uid 500); 7 Jun 2014 14:12:28 -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 99222 invoked by uid 99); 7 Jun 2014 14:12:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 14:12:28 +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 mohajeri@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 14:12:24 +0000 Received: by mail-ob0-f175.google.com with SMTP id wo20so4031345obc.20 for ; Sat, 07 Jun 2014 07:12:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=wFzER4vK5U60CGny6gLkpPeaB2V+V4l1B2d8I2xYtuM=; b=lPI10gxIJdDW3kGI+JwY4xb+04+VXw/R975iYJYI57/Ay8bQoH+hLIgESsuvw64mZ3 Eknk0pjFjoQB7+geI2V7ITn2NfhoFfoYNjggEMqGonx6p26iX8i2xoRHo0kKzOU9SATm 0K6l4KDKJPC4VrgqPN0lZpQwObEXxK4zmeX2fHzDoU57nOlItxpzMAGNaK5b257mcKL5 vbGFv5P5aXcOmr1IG7fwtX8Ixen2wmw+cCoAgZFjTJvUhVXN58l4wNBmHWPtT0qINmwt eVTWNBmxeUoHWoJ8JGyejSHOygA+IEDC/a7ebxaMwuz7yj5Q6AY2JDwJPiVOVL2OUocY dpEQ== MIME-Version: 1.0 X-Received: by 10.60.175.163 with SMTP id cb3mr13736775oec.29.1402150323773; Sat, 07 Jun 2014 07:12:03 -0700 (PDT) Received: by 10.182.204.1 with HTTP; Sat, 7 Jun 2014 07:12:03 -0700 (PDT) In-Reply-To: <869970D71E26D7498BDAC4E1CA92226B86F1A3F9@MBX021-E3-NJ-2.exch021.domain.local> References: <869970D71E26D7498BDAC4E1CA92226B86F1A3F9@MBX021-E3-NJ-2.exch021.domain.local> Date: Sat, 7 Jun 2014 10:12:03 -0400 Message-ID: Subject: Re: Gathering connection information From: Peyman Mohajerian To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bd75f24f86a1d04fb3f8f41 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd75f24f86a1d04fb3f8f41 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In my experience you build a node called Edge Node which has all the libraries and configuration setting in XML to connect to the cluster, it just doesn't have any of the Hadoop daemons running. On Wed, Jun 4, 2014 at 2:46 PM, John Lilley wrote: > We=E2=80=99ve found that much of the Hadoop samples assume that running = is being > done form a cluster node, and that the connection information can be > gleaned directly from a configuration object. However, we always run our > client from a remote computer, and our users must manually specify the > NN/RM addresses and ports. We=E2=80=99ve found this varies maddeningly b= etween > distros and especially on hosted virtual implementations. Getting the > wrong port results in various inscrutable errors with red-herring message= s > about security. Is there a prescribed way to get the correct connection > information more easily, like from a web API (where at least we=E2=80=99d= only need > one address and port)? > > > > john > > > --047d7bd75f24f86a1d04fb3f8f41 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In my experience you build a node called Edge Node which h= as all the libraries and configuration setting in XML to connect to the clu= ster, it just doesn't have any of the Hadoop daemons running.=C2=A0


On Wed, Jun 4, 2014 at 2:46 PM, John Lil= ley <john.lilley@redpoint.net> wrote:

We=E2=80=99ve found that much of the Hadoop samples = assume that running is being done form a cluster node, and that the connect= ion information can be gleaned directly from a configuration object.=C2=A0 = However, we always run our client from a remote computer, and our users must manually specify the NN/RM addresses and port= s.=C2=A0 We=E2=80=99ve found this varies maddeningly between distros and es= pecially on hosted virtual implementations.=C2=A0 Getting the wrong port re= sults in various inscrutable errors with red-herring messages about security.=C2=A0 Is there a prescribed way to get the correc= t connection information more easily, like from a web API (where at least w= e=E2=80=99d only need one address and port)?

=C2=A0

john

=C2=A0


--047d7bd75f24f86a1d04fb3f8f41--