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 new developments the latter will be better in the coming months.
I would STRONGLY recommend getting a 4-disk RAID setup for the WebDB. That
is your main bottleneck. 1-2 NICS is fine
So here's a look at the setup
1. "Souped-up" DB server - Dual CPU, 4 GB Ram (min) RAID 5 or 10, 1-2 NICS
This is the 'fetcher' server?
2. Basic Search Servers - Single/Dual CPU, Maximum RAM, Single IDE/SATAThese are the 'fetched' segment backup and search servers?
drive (or 2 for redundancy)
If I have 10 Million pages / server, this is good thing: 2kbyte * 10 = 20 GByte RAM? Or there is enought 10 GByte, and later put more if it need?
3. Basic Web Servers - Single/Dual CPU, Medium RAMIn this boxs I will put 1-2 GByte RAM.
I would like put frontend Apache2 and mod_jk2, this is bottleneck, or in this way I will tunning somethings: static images, web pages etc. caching? Or better way Tomcats directly to the WEB?
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Nutch-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-general
