Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of c0d3h4ck@gmail.com designates
 209.85.200.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=eODBTmyCA2yyjc7GMhTNT6YExU/3Lg6THmows9eAIfkAEZlIPoaN7O2p5hKNIM/O83
         mPjvSGPAVgdp2tVpHMHrQRFUi3lWuYeHfJyqY6ulOfd+caPmr5IVIpZVZZ7Ff0iRabdK
         /EfcZL+S/5LziksdxfjCWUHhNuhf5lwbPIVWc=
Message-ID: <4b2c7b610901050228o6bfeed4bndee5a1e9e1bccb4e@mail.gmail.com>
Date: Mon, 5 Jan 2009 19:28:48 +0900
From: "Hyunsik Choi" <c0d3h4ck@gmail.com>
To: core-user@hadoop.apache.org
Subject: Why doesn't hadoop invoke the topology script with only IP address as
 the argument?
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I tried to use the topology script defined by
topology.script.file.name property in order for rack awareness. After
setting and restart hadoop, I ran the wordcount example to test rack
awareness. However, some hosts are assigned to valid rack IDs produced
by ip address, but others are assigned to invalid rack IDs produced by
hostnames.

In order to find the problem, I added dump code to the topology script
file in order to store all given arguments to certain file.
As a result, I knew that in most times the topology script file is
called by IP address but in some case it is called by hostname.

Is it correct?

--
Hyunsik Choi
Database & Information Systems Group,
Korea University