Erick, I agree, but... wouldn't it be SO COOL if it did work! Avoid all the
ridiculous complexity of "cloud".
Have a temporary lock to permit and exclude updates.
-- Jack Krupansky
-----Original Message-----
From: Erick Erickson
Sent: Thursday, June 26, 2014 12:37 PM
To: solr-user@lucene.apache.org
Subject: Re: Two solr instances access common index
bq: But my scenario is that both solr instances would write to the common
directory
Do NOT do this. Don't even try. I guarantee Bad Things Will Happen.
Why do you want to do this? To save disk space? Accomplish NRT
searching on multiple machines?
Please define the problem you're trying to solve and why existing supported
ways of using Solr wouldn't work for you, e.g. SolrCloud or master/slave
setups before asking for a specific solution, as this sounds very much like
an
XY problem.
Best,
Erick
On Thu, Jun 26, 2014 at 4:25 AM, Prasi S <prasi1...@gmail.com> wrote:
Can you please tell me whihc solr version you have tried with? I tried
giving
<lockType>${solr.lock.type:none}</lockType> in 2 solr instances and now it
is working. I am not getting the write lock exception when starting the
second instance.
But my scenario is that both solr instances would write to the common
directory ( but not both simultaneously for sure). Is there any drawback
of
using "noLock"
Please advice.
Thanks,
Prasi
On Thu, Jun 26, 2014 at 3:20 PM, Uwe Reh <r...@hebis.uni-frankfurt.de>
wrote:
Hi,
with the lock type 'simple' I have tree instances (different JREs,
GC-Problem) running on the same files.
You should use this option only for a readonly system. Otherwise it's
easy
to corrupt the index.
Maybe you should have a look on replication or SolrCloud.
Uwe
Am 26.06.2014 11:25, schrieb Prasi S:
Hi,
Is it possible to point two solr instances to point to a common index
directory. Will this work wit changing the lock type?
Thanks,
Prasi
