thanks for your response - i've been waiting for this very
clarification. so 'commit()' makes readers re-read the indexes?
On Feb 26, 2008, at 7:03 PM, Mike Klaas wrote:
There hasn't really been a concrete answer given in this thread,
so: It works to point multiple Solr's at a single data dir, but you
can't have more than one writer. If you try, the index could become
corrupted or inconsistent (especially if you are using 'simple' lock
type). Also, the Solrs do not communicate with each other. You
have to tell the readers manually that the index is updated (via
commit()--autoCommit will not work).
-Mike
On 26-Feb-08, at 9:39 AM, Alok Dhir wrote:
Are you saying all the servers will use the same 'data' dir? Is
that a supported config?
On Feb 26, 2008, at 12:29 PM, Matthew Runo wrote:
We're about to do the same thing here, but have not tried yet. We
currently run Solr with replication across several servers. So
long as only one server is doing updates to the index, I think it
should work fine.
Thanks!
Matthew Runo
Software Developer
Zappos.com
702.943.7833
On Feb 26, 2008, at 7:51 AM, Evgeniy Strokin wrote:
I know there was such discussions about the subject, but I want
to ask again if somebody could share more information.
We are planning to have several separate servers for our search
engine. One of them will be index/search server, and all others
are search only.
We want to use SAN (BTW: should we consider something else?) and
give access to it from all servers. So all servers will use the
same index base, without any replication, same files.
Is this a good practice? Did somebody do the same? Any problems
noticed? Or any suggestions, even about different configurations
are highly appreciated.
Thanks,
Gene
