Hi Subir,

For me it was a ssh configuration issue.
Steps taken

1. Executed the "start-mapred.sh"
2. Got the "ssh_exchange_identification closed by remote host"
3. Tried connecting to the same machine using ssh (ssh localhost).
Secondary node was not able to do a "ssh localhost".
4. Configured this and finally got it working

Hope this saves someone's  time !!

Thanks

On Fri, Mar 9, 2012 at 2:28 AM, Subir S <subir.sasiku...@gmail.com> wrote:

> what was the solution?
>
> On Fri, Mar 9, 2012 at 2:03 PM, Atul Thapliyal <aatul.thapli...@gmail.com
> >wrote:
>
> > Hello Hadoop users,
> >
> > Issue described here is resolved now.
> >
> > Thanks
> >
> > On Thu, Mar 8, 2012 at 10:51 PM, Atul Thapliyal
> > <aatul.thapli...@gmail.com>wrote:
> >
> > > Hi Hadoop users,
> > >
> > > I am new member and please let me know if this is not the correct
> format
> > > to ask questions.
> > >
> > > I am trying to setup a small Hadoop cluster where I will run Pig
> queries.
> > > Hadoop cluster is running fine but when I run a pig query it just
> hangs.
> > >
> > > Note - Pig runs fine in local mode
> > >
> > > So I narrowed down the errors to the following -
> > >
> > > I have a secondary name node on a different machine (.e.g node 2).
> > >
> > > Point 1.
> > > When I execute start-mapred.sh on node 2, I get
> > > "ssh_exchange_identification closed by remote host" message. BUT the
> > > secondary name node starts with no error messages in the log
> > > I can even access it through port 50030
> > >
> > > So far no errors
> > >
> > > Point 2.
> > > When I try to run a map-reduce job. I get a "java.net.ConnectException:
> > > Connection refused" error in the secondary name node log files.
> > >
> > > Are point 1 and point 2 related
> > >
> > > Any hints / pointers on how to solve this ? Also, ssh time out is set
> to
> > > 20 so I am assuming that error is not because of this.
> > >
> > > Thanks for reading
> > >
> > > --
> > > Warm Regards
> > > Atul
> > >
> >
> >
> >
> > --
> > Warm Regards
> > Atul
> >
>



-- 
Warm Regards
Atul

Reply via email to