Return-Path: X-Original-To: apmail-whirr-dev-archive@www.apache.org Delivered-To: apmail-whirr-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5669D105FD for ; Sun, 6 Oct 2013 13:13:44 +0000 (UTC) Received: (qmail 29106 invoked by uid 500); 6 Oct 2013 13:13:43 -0000 Delivered-To: apmail-whirr-dev-archive@whirr.apache.org Received: (qmail 28999 invoked by uid 500); 6 Oct 2013 13:13:43 -0000 Mailing-List: contact dev-help@whirr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@whirr.apache.org Delivered-To: mailing list dev@whirr.apache.org Received: (qmail 28990 invoked by uid 99); 6 Oct 2013 13:13:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Oct 2013 13:13:42 +0000 Date: Sun, 6 Oct 2013 13:13:41 +0000 (UTC) From: "Przemyslaw Pastuszka (JIRA)" To: dev@whirr.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (WHIRR-749) Invalid hostname in fs.default.name in core-site.xml on ec2 cluster 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/WHIRR-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Przemyslaw Pastuszka updated WHIRR-749: --------------------------------------- Attachment: hadoop.properties > Invalid hostname in fs.default.name in core-site.xml on ec2 cluster > ------------------------------------------------------------------- > > Key: WHIRR-749 > URL: https://issues.apache.org/jira/browse/WHIRR-749 > Project: Whirr > Issue Type: Bug > Affects Versions: 0.8.2 > Reporter: Przemyslaw Pastuszka > Attachments: hadoop.properties > > > Tried to provision ec2 cluster using hadoop.properties (attached) file and whirr-0.8.2. Provisioning ended without any exception, but actually hadoop cluster was not usable - this was due to wrong addresses being configured in core-site.xml: > {code} > > fs.default.name > hdfs://hadoop-37f7a94f:8020/ > > > {code} > but system doesn't know such hostname: > {code} > $ ping hadoop-37f7a94f > ping: unknown host hadoop-37f7a94f > {code} > As a result none of hadoop processes is working on the cluster - as a proof, that hostname is the root cause of the problem, here's excerpt from namenode logs: > {code} > 2013-10-06 11:46:55,872 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.net.UnknownHostException: Invalid hostname for server: hadoop-37f7a94f > at org.apache.hadoop.ipc.Server.bind(Server.java:275) > at org.apache.hadoop.ipc.Server$Listener.(Server.java:341) > at org.apache.hadoop.ipc.Server.(Server.java:1539) > at org.apache.hadoop.ipc.RPC$Server.(RPC.java:569) > at org.apache.hadoop.ipc.RPC.getServer(RPC.java:530) > at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:324) > at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:569) > at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1479) > at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1488) > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)