Hi!
I meant to reply a few days ago when I found the problem, but forgot
to do so until now :))
The problem was that the settings for fs.default.name and
mapred.job.tracker in hadoop-site.xml were using the DNS name of the
master server. When I changed the value from the DNS name to the IP
address of the master server, I started seeing some output. I'm not
sure why the DNS name wasn't able to be resolved... I wasn't seeing
this problem with hadoop 16.1. Also, nothing about this problem was
written to the logs which is why it took so long to find it!
Shirley
On Sep 7, 2008, at 8:38 AM, 叶双明 wrote:
Are you sure there isn't any error or exception in logs?
2008/9/5, Shirley Cohen <[EMAIL PROTECTED]>:
Hi Dmitry,
Thanks for your suggestion. I checked and the other systems on the
cluster
do seem to have java installed. I was also able to run the job in
single
mode on the cluster. However, as soon as I add the others 15 nodes
to the
slaves file and re-run the job, the problem appears (i.e. there is
zero
output).
I guess I was going to wait to see if anyone else have seen this
problem
before submitting a bug report.
Shirley
On Sep 4, 2008, at 1:37 PM, Dmitry Pushkarev wrote:
Hi,
I'd check java version installed, that was the problem in my
case, and
surprisingly no output from hadoop. If it help - can you submit bug
request
? :)
-----Original Message-----
From: Shirley Cohen [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2008 10:07 AM
To: [email protected]
Subject: no output from job run on cluster
Hi,
I'm running on hadoop-0.18.0. I have a m-r job that executes
correctly in standalone mode. However, when run on a cluster, the
same job produces zero output. It is very bizarre. I looked in the
logs and couldn't find anything unusual. All I see are the usual
deprecated filesystem name warnings. Has this ever happened to
anyone? Do you have any suggestions on how I might go about
diagnosing the problem?
Thanks,
Shirley
--
Sorry for my englist!! 明
