From yarn-dev-return-953-apmail-hadoop-yarn-dev-archive=hadoop.apache.org@hadoop.apache.org Wed Feb 20 19:51:15 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 3E04EDDCD for ; Wed, 20 Feb 2013 19:51:15 +0000 (UTC) Received: (qmail 42846 invoked by uid 500); 20 Feb 2013 19:51:14 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 42790 invoked by uid 500); 20 Feb 2013 19:51:14 -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 42680 invoked by uid 99); 20 Feb 2013 19:51:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 19:51:14 +0000 Date: Wed, 20 Feb 2013 19:51:14 +0000 (UTC) From: "Hitesh Shah (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (YARN-130) Yarn examples use wrong configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-130. ------------------------------ Resolution: Fixed Closing this out as this was addressed as part of YARN-277. > Yarn examples use wrong configuration > ------------------------------------- > > Key: YARN-130 > URL: https://issues.apache.org/jira/browse/YARN-130 > Project: Hadoop YARN > Issue Type: Bug > Components: applications > Affects Versions: 2.0.3-alpha > Reporter: Erich Schubert > Priority: Minor > > AFAICT the example applications are broken when you don't use default ports. So it probably won't show in a single node setup. > The bug fix seems to be: > - conf = new Configuration(); > + conf = new YarnConfiguration(); > Then the yarn settings file (containing relevant host and port information) will also be read. > The error messages *need* to be improved. For me, they said something like "protocol not supported". The reason was that a different hadoop RPC was running on the port it was connecting to. It took me a lot of debugging to find out that it was just talking to the wrong service because it had not read it's configuration file... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira