Doug Cutting wrote:
Shawn Gervais wrote:
I was not able to use the literal instructions, as my indexes and
segments are in DFS while the document presumes a local filesystem
installation
Search performance is not good with DFS-based indexes & segments. This
is not recommended.
Yeah, I figured - ignoring network overhead it seems that it would
prevent the OS from caching disk pages, no?
Distributed search is not meant for a single merged index, but rather
for searching multiple indexes. With distributed search, each node will
typically have (a local copy of) a few segments and either a merged
index for just those segments, or separate indexes for each segment.
What is the best way to maintain an operational fetch/index and search
cluster? It seems that it would help to have a tool that was able to
partition existing segments and indexes and export those to the local
filesystems of the slave nodes.
Should I coordinate my fetches and indexing so that the resultant
segments/indexes are optimal for each of my slave nodes? How do others
handle dissimilar search slave nodes?
Regards,
-Shawn
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Nutch-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-general
