That's why i don't recommend it. Nutch 2.x will be able to recover from fetch 
and parse jobs that have been terminated.

> Killing nutch in a middle of job can cause segments corruption. I have
> observed it many times. So CRTL+C isn't good advice.
> 
> And I don't know the answer either. :(
> 
> Best Regards
> Alexander Aristov
> 
> On 4 November 2010 22:00, Markus Jelsma <markus.jel...@openindex.io> wrote:
> > Kill it! I guess it just runs standalone, just like executed jobs from
> > the command line which you can just terminate with CTRL+C.
> > 
> > I don't recommend stopping Nutch while executing jobs, especially the
> > fetch and parse jobs because they cannot be resumed in Nutch 1.x.
> > 
> > > I am using Drupal/ApacheSolr/Nutch 1.2
> > > 
> > > It uses hadoop for the logs. The jobs are started in Nutch module for
> > > Drupal so perhaps this is too blank of an issue to even try and discus
> > > here. I would hate to waste your time.
> > > 
> > > I just can't find a way to stop and restart a crawl anywhere for 1.2
> > > 
> > > -----Original Message-----
> > > From: Markus Jelsma [mailto:markus.jel...@openindex.io]
> > > Sent: Thursday, November 04, 2010 11:41 AM
> > > To: user@nutch.apache.org
> > > Cc: Eric Martin
> > > Subject: Re: Stop Nutch
> > > 
> > > How did you start it? Are you running it on Hadoop at all?
> > > 
> > > > I can't find a way to stop Nutch 1.2 via command line. I use the
> > > > stop-all.sh command and it says:
> > > > 
> > > > 
> > > > 
> > > > r...@we [/lib/nutch/bin]# ./stop-all.sh
> > > > 
> > > > no jobtracker to stop
> > > > 
> > > > r...@localhost's password:
> > > > 
> > > > localhost: no tasktracker to stop
> > > > 
> > > > localhost: stdin: is not a tty
> > > > 
> > > > no namenode to stop
> > > > 
> > > > 
> > > > 
> > > > I have been searching google but I can't find anything else to guide
> > 
> > me.
> > 
> > > > I am using Drupal 6/Solr/Nutch 1.2
> > > > 
> > > > 
> > > > 
> > > > Any ideas on where I am going wrong for stopping it? Should I just
> > > > reboot?
> > > > 
> > > > 
> > > > 
> > > > Eric

Reply via email to