David Wei wrote:
Steve Loughran ??:
David Wei wrote:
Error initializing attempt_200810220716_0004_m_000001_0:
java.lang.IllegalArgumentException: Wrong FS:
hdfs://192.168.52.129:9000/tmp/hadoop-root/mapred/system/job_200810220716_0004/job.xml,
expected: hdfs://datacenter5:9000 at
org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:320)
And if I configure the masters/slaves with hostname, datanode will
not be able to connect to the master!
No one knows how to solve this?
that implies DNS problems. what does
nslookup datacenter5
return on the command line of all the slaves?
Steve,
the output is:
Server: 192.168.18.10
Address: 192.168.18.10#53
Non-authoritative answer:
Name: datacenter5.papa
Address: 61.140.3.66
And none of them is the address of datacenter5(192.168.52.129). How can
I solve this problem?
well, your datacenter5 hostname may be the public IP address; the
192.168. addresses are the addresses within the cluster. Because they
are different, and because the namenode thinks it is called datacenter5,
things are breaking
Some options
-bring up your own DNS server and add the entries for the hostnames
-edit /etc/hosts in the different servers (this becomes expensive after
a while, and if one machine gets inconsistent, you will have a hard time
tracking down the problem)
-somehow get the namenode to come up with a filesystem called
hdfs://192.168.52.129:9000/. That should be something you can do in the
site fs.default.name option.