Re: what's going on :( ?

2009-02-12 Thread Mark Kerzner
I see it is picking up other parameters from config, so my hypothesis is
that in 0.19 the file system is listening on 8020. I went back to 18.3 and
also did not change this hdfs port this time, preempting the question, so I
am fine for now.
Mark

On Thu, Feb 12, 2009 at 1:40 AM, Rasit OZDAS  wrote:

> Hi, Mark
>
> Try to add an extra property to that file, and try to examine if
> hadoop recognizes it.
> This way you can find out if hadoop uses your configuration file.
>
> 2009/2/10 Jeff Hammerbacher :
> > Hey Mark,
> >
> > In NameNode.java, the DEFAULT_PORT specified for NameNode RPC is 8020.
> > From my understanding of the code, your fs.default.name setting should
> > have overridden this port to be 9000. It appears your Hadoop
> > installation has not picked up the configuration settings
> > appropriately. You might want to see if you have any Hadoop processes
> > running and terminate them (bin/stop-all.sh should help) and then
> > restart your cluster with the new configuration to see if that helps.
> >
> > Later,
> > Jeff
> >
> > On Mon, Feb 9, 2009 at 9:48 PM, Amar Kamat  wrote:
> >> Mark Kerzner wrote:
> >>>
> >>> Hi,
> >>> Hi,
> >>>
> >>> why is hadoop suddenly telling me
> >>>
> >>>  Retrying connect to server: localhost/127.0.0.1:8020
> >>>
> >>> with this configuration
> >>>
> >>> 
> >>>  
> >>>fs.default.name
> >>>hdfs://localhost:9000
> >>>  
> >>>  
> >>>mapred.job.tracker
> >>>localhost:9001
> >>>
> >>
> >> Shouldnt this be
> >>
> >> hdfs://localhost:9001
> >>
> >> Amar
> >>>
> >>>  
> >>>  
> >>>dfs.replication
> >>>1
> >>>  
> >>> 
> >>>
> >>> and both this http://localhost:50070/dfshealth.jsp and this
> >>> http://localhost:50030/jobtracker.jsp links work fine?
> >>>
> >>> Thank you,
> >>> Mark
> >>>
> >>>
> >>
> >>
> >
>
>
>
> --
> M. Raşit ÖZDAŞ
>


Re: what's going on :( ?

2009-02-11 Thread Rasit OZDAS
Hi, Mark

Try to add an extra property to that file, and try to examine if
hadoop recognizes it.
This way you can find out if hadoop uses your configuration file.

2009/2/10 Jeff Hammerbacher :
> Hey Mark,
>
> In NameNode.java, the DEFAULT_PORT specified for NameNode RPC is 8020.
> From my understanding of the code, your fs.default.name setting should
> have overridden this port to be 9000. It appears your Hadoop
> installation has not picked up the configuration settings
> appropriately. You might want to see if you have any Hadoop processes
> running and terminate them (bin/stop-all.sh should help) and then
> restart your cluster with the new configuration to see if that helps.
>
> Later,
> Jeff
>
> On Mon, Feb 9, 2009 at 9:48 PM, Amar Kamat  wrote:
>> Mark Kerzner wrote:
>>>
>>> Hi,
>>> Hi,
>>>
>>> why is hadoop suddenly telling me
>>>
>>>  Retrying connect to server: localhost/127.0.0.1:8020
>>>
>>> with this configuration
>>>
>>> 
>>>  
>>>    fs.default.name
>>>    hdfs://localhost:9000
>>>  
>>>  
>>>    mapred.job.tracker
>>>    localhost:9001
>>>
>>
>> Shouldnt this be
>>
>> hdfs://localhost:9001
>>
>> Amar
>>>
>>>  
>>>  
>>>    dfs.replication
>>>    1
>>>  
>>> 
>>>
>>> and both this http://localhost:50070/dfshealth.jsp and this
>>> http://localhost:50030/jobtracker.jsp links work fine?
>>>
>>> Thank you,
>>> Mark
>>>
>>>
>>
>>
>



-- 
M. Raşit ÖZDAŞ


Re: what's going on :( ?

2009-02-10 Thread Jeff Hammerbacher
Hey Mark,

In NameNode.java, the DEFAULT_PORT specified for NameNode RPC is 8020.
>From my understanding of the code, your fs.default.name setting should
have overridden this port to be 9000. It appears your Hadoop
installation has not picked up the configuration settings
appropriately. You might want to see if you have any Hadoop processes
running and terminate them (bin/stop-all.sh should help) and then
restart your cluster with the new configuration to see if that helps.

Later,
Jeff

On Mon, Feb 9, 2009 at 9:48 PM, Amar Kamat  wrote:
> Mark Kerzner wrote:
>>
>> Hi,
>> Hi,
>>
>> why is hadoop suddenly telling me
>>
>>  Retrying connect to server: localhost/127.0.0.1:8020
>>
>> with this configuration
>>
>> 
>>  
>>fs.default.name
>>hdfs://localhost:9000
>>  
>>  
>>mapred.job.tracker
>>localhost:9001
>>
>
> Shouldnt this be
>
> hdfs://localhost:9001
>
> Amar
>>
>>  
>>  
>>dfs.replication
>>1
>>  
>> 
>>
>> and both this http://localhost:50070/dfshealth.jsp and this
>> http://localhost:50030/jobtracker.jsp links work fine?
>>
>> Thank you,
>> Mark
>>
>>
>
>


Re: what's going on :( ?

2009-02-09 Thread Amar Kamat

Mark Kerzner wrote:

Hi,
Hi,

why is hadoop suddenly telling me

 Retrying connect to server: localhost/127.0.0.1:8020

with this configuration


  
fs.default.name
hdfs://localhost:9000
  
  
mapred.job.tracker
localhost:9001
  

Shouldnt this be

hdfs://localhost:9001

Amar

  
  
dfs.replication
1
  


and both this http://localhost:50070/dfshealth.jsp and this
http://localhost:50030/jobtracker.jsp links work fine?

Thank you,
Mark

  




what's going on :( ?

2009-02-09 Thread Mark Kerzner
Hi,
Hi,

why is hadoop suddenly telling me

 Retrying connect to server: localhost/127.0.0.1:8020

with this configuration


  
fs.default.name
hdfs://localhost:9000
  
  
mapred.job.tracker
localhost:9001
  
  
dfs.replication
1
  


and both this http://localhost:50070/dfshealth.jsp and this
http://localhost:50030/jobtracker.jsp links work fine?

Thank you,
Mark