Dear Chirag,
Thanks for your answer and your time.
Some other questions to your mail.
In that case a central DB server would be okay, and you can move the
segments around using rsync to the search servers. I've found this to be a
more hassle-free solution that using NDFS, but I'm certain given the
1. Souped-up DB server - Dual CPU, 4 GB Ram (min) RAID 5 or 10, 1-2
NICS
This is the 'fetcher' server?
This is you fetch/crawler/indexer -- create the final segments here, then
move them to the search server. That way if a search server goes down,
simply move the segment to another server.
: RE: [Nutch-general] RE: Nutch - new public server
1. Souped-up DB server - Dual CPU, 4 GB Ram (min) RAID 5 or 10, 1-2
NICS
This is the 'fetcher' server?
This is you fetch/crawler/indexer -- create the final segments here,
then
move them to the search server. That way if a search
@incubator.apache.org
Subject: RE: [Nutch-general] RE: Nutch - new public server
To add from my experiences:
I've preferred Resin (stability performance)
I always go for more ram than more servers. It's cheaper in the long run
when it comes to man hours and service as well as MTBF for your hardware.
Use
