Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 B0223D5C1 for ; Wed, 17 Oct 2012 21:52:02 +0000 (UTC) Received: (qmail 70546 invoked by uid 500); 17 Oct 2012 21:51:58 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 70409 invoked by uid 500); 17 Oct 2012 21:51:57 -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 70400 invoked by uid 99); 17 Oct 2012 21:51:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2012 21:51:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of adi@cloudera.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2012 21:51:53 +0000 Received: by mail-ie0-f176.google.com with SMTP id k11so14707471iea.35 for ; Wed, 17 Oct 2012 14:51:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=2aYRZKBicJqBFGvi1dz3LUmEmN03sRB3FmPS65SFHQs=; b=oaVu+sAjoWqbwjBAVonfmlYwX/AB0pZjbtxe5jijUYT5AtDS8ioaeVD/yiERtyfBqz QyAOMkFw4bbffY01cv00JbQ5CsDCuHcR9ZZhvOsInt5nxPmsIR/Kv93Z6yd91Zijd5M+ EnwvBQLijTvE6ZImlQCapU7BkvXeLzzYNHcwTl403exyvs2vf7Bno+qE0TKQ+il8cn8u a2cdU80gpGapvVh9Cb3jb/oWyQ4SyWpZtbpTLa0G5zCzqQfR5AwRzSYgQPd/YSUAsfAs yesPvgbwvihz+qmydRYMPJfPoutQRISyxP5HH81ITnSvkTA3ZZBt+DMETJjFOWqvJGmr Fczg== MIME-Version: 1.0 Received: by 10.50.40.133 with SMTP id x5mr3043622igk.32.1350510692317; Wed, 17 Oct 2012 14:51:32 -0700 (PDT) Received: by 10.64.124.3 with HTTP; Wed, 17 Oct 2012 14:51:32 -0700 (PDT) In-Reply-To: <1350507871.11114.YahooMailNeo@web194702.mail.sg3.yahoo.com> References: <1350507871.11114.YahooMailNeo@web194702.mail.sg3.yahoo.com> Date: Wed, 17 Oct 2012 14:51:32 -0700 Message-ID: Subject: Re: Does Hadoop Require Public IP address to create a cluster. From: Andy Isaacson To: user@hadoop.apache.org, Sundeep Kambhmapati Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQn+/Usl2B39Z3D8K4F+0Hvg/9jVbqNQmDZTs+rKHlKabMCLGKWUGd1pN8QF37siguCiFJqi X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Oct 17, 2012 at 2:04 PM, Sundeep Kambhmapati wrote: > I am trying to install Hadoop 0.20.2 on a cluster on two virtual machines. > One acting as master other as slave. > I am able to ssh from master to slave and vice verse. But when I run > start-dfs.sh namenode is not starting. > I checked the namenode log it says: > org.apache.hadoop.hdfs.server.namenode.NameNode: java.net.BindException: > Problem binding to sk.r252.0/10.2.252.0:54310 : Cannot assign requested > address > > 10.2.252.0 is the Private IP address of the Virtual machine in the cluster > (master-sk.r252.0). > Does Hadoop require that all the nodes in the cluster to have separate Pubic > IP address to setup hadoop cluster. Hadoop does not require public IP addresses. I routinely run a multinode cluster on 192.168.x.y using several VMs in a "NAT" configuration. This configuration works best if you have consistent "hostname" and IP addresses. I use .local, .local, etc using Avahi for IP autoconfiguration in the .local TLD, but you can also hardcode IP addresses in /etc/hosts on each node or use DNS. Try "ping " to see if name lookup is working. Your hostnames look very odd, having ".0" for your top-level domain is likely to confuse things. Try fixing it to be .internal or something along those lines. The "cannot assign requested address" looks like your namenode configuration does not match the IP addresses on the node you're trying to start the namenode on. Double-check your master file, /etc/hosts and "ifconfig -a" settings, and hdfs-site.xml settings. -andy