[KinoSearch] KinoSearch::Docs::Cookbook::ReusingSearchers

[Henry]

> What we need is to do is break up nodes by task.  We'll have a
> dedicated lexicon server, a dedicated document server, one or more
> master search nodes, and multiple machines dedicated to the task of
> crunching through posting lists.  The lexicon server and the document
> server will be abstractions behind which one or more machines will sit.

OK - this makes things a bit more involved from an admin perspective - and
also requires a lot more hardware (if I understand your proposed
architecture correctly).

Correct me if I'm wrong:  instead of chopping up the index into smaller
and smaller sub-indexes (spread across multiple 'master' search nodes) to
improve performance and handle concurrent search load, you're proposing
separate physical machines with specialized roles/tasks (lexicon, docs,
search)?

By "multiple machines dedicated to the task of crunching through posting
lists" I presume you mean the indexing machines?

Forgive my ignorance, I'm just wondering whether the benefits of this
approach outweigh the elegance of many simple master nodes and the way it
dovetails with classic clustering.  ie, I need more performance, I just
add more master nodes and re-divide the index across all nodes; the same
principle applies when the corpus and index grows - just chop it up into
smaller and smaller pieces across more and more nodes.

Regards
Henry


_______________________________________________
KinoSearch mailing list
KinoSearch at rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch