On Tue, Oct 17, 2006 at 01:14:18PM -0700, Robert Firby wrote:
> I had a problem just like this when I upgraded too. It fixed my problem to
> change the machine names in the hadoop.site.xml file to be fully qualified.
>
> Ie. Change prodigy:50006 to be prodigy.whatever.com:50006
>
It turns out t
On Tue, Oct 17, 2006 at 01:14:18PM -0700, Robert Firby wrote:
> I had a problem just like this when I upgraded too. It fixed my problem to
> change the machine names in the hadoop.site.xml file to be fully qualified.
>
> Ie. Change prodigy:50006 to be prodigy.whatever.com:50006
>
Weird. I'll g
I had a problem just like this when I upgraded too. It fixed my problem to
change the machine names in the hadoop.site.xml file to be fully qualified.
Ie. Change prodigy:50006 to be prodigy.whatever.com:50006
Jim
On 10/17/06 12:19 PM, "Andrew McNabb" <[EMAIL PROTECTED]> wrote:
> I just upgrad
I just upgraded from Hadoop 0.6.2 to 0.7.1. I'm having a new networking
problem now. My mapred.job.tracker now only listens on localhost
(127.0.0.1). All of the other services seem to be behaving correctly.
In hadoop-site.xml, I have mapred.job.tracker set to "prodigy:50006" and
fs.default.name t
