two nutch indexes on same webserver

["Insurance Squared Inc." <gc...@insurancesquared.com>]

Hi All,

We've been running nutch on one website on our server, we've just added 
a second website that's running nutch on a seperate 
index/crawl/segments.  We're experiencing some difficulty getting things 
running and seperating the two.  Not entirely sure that the difficulty 
is with nutch or tomcat or what - or a whole bunch of both.

Would anyone be able to give a rough and dirty idea of how this should 
be set up?  We don't have any specific questions (everything's broken :) 
) but a general outline of what we should be doing to accomplish two 
nutch sites on one webserver would be a big help.

(I thought this was covered recently as well, but didn't see it in the 
archives.  And it seems like nutchhacks.com is now down).

Thanks,
g.

Re: two nutch indexes on same webserver

[Dennis Kubes <nu...@dragonflymc.com>]

Assuming you have two separate war files deployed, it should be as easy 
as setting the searcher.dir property in the nutch-site.xml file in the 
different web-inf directories to the separate index locations.  If you 
want to go the distributed searching route there is a in depth 
explanation on the NutchHadoopTutorial on the Nutch Wiki.

Dennis

Insurance Squared Inc. wrote:
> Hi All,
>
> We've been running nutch on one website on our server, we've just 
> added a second website that's running nutch on a seperate 
> index/crawl/segments.  We're experiencing some difficulty getting 
> things running and seperating the two.  Not entirely sure that the 
> difficulty is with nutch or tomcat or what - or a whole bunch of both.
>
> Would anyone be able to give a rough and dirty idea of how this should 
> be set up?  We don't have any specific questions (everything's broken 
> :) ) but a general outline of what we should be doing to accomplish 
> two nutch sites on one webserver would be a big help.
>
> (I thought this was covered recently as well, but didn't see it in the 
> archives.  And it seems like nutchhacks.com is now down).
>
> Thanks,
> g.
>