On 3/6/2018 2:08 PM, Terry Steichen wrote:
> Is it possible to run solr in a read-only directory?
Solr can be installed as a service on most operating systems other than
Windows. A service installer script comes with the download. It is
installed to run as an unprivileged user, "solr" by default
...@sematext.com]
Sent: Wednesday, 7 March 2018 10:19 p.m.
To: solr-user@lucene.apache.org
Subject: Re: Solr Read-Only?
Hi Terry,
Maybe you can try alternative approaches like putting some proxy in front of
Solr and configure it to let only certain URLs. Other option is to define
custom update
Hi Terry,
Maybe you can try alternative approaches like putting some proxy in front of
Solr and configure it to let only certain URLs. Other option is to define
custom update request processor chain that will not include
RunUpdateProcessorFactory - that will prevent accidental index updates.
HT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Terry,
On 3/6/18 4:55 PM, Terry Steichen wrote:
> Chris,
>
> Thanks for your suggestion. Restarting solr after an in-memory
> corruption is, of course, trivial (compared to rebuilding the
> indexes).
>
> Are there any solr directories that MUST
Chris,
Thanks for your suggestion. Restarting solr after an in-memory
corruption is, of course, trivial (compared to rebuilding the indexes).
Are there any solr directories that MUST be read/write (even with a
pre-built index)? Would it suffice (for my purposes) to make only the
data/index dire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Terry,
On 3/6/18 4:08 PM, Terry Steichen wrote:
> Is it possible to run solr in a read-only directory?
>
> I'm running it just fine on a ubuntu server which is accessible
> only through SSH tunneling. At the platform level, this is fine:
> only au
Is it possible to run solr in a read-only directory?
I'm running it just fine on a ubuntu server which is accessible only
through SSH tunneling. At the platform level, this is fine: only
authorized users can access it (via a browser on their machine accessing
a forwarded port).
The problem is t
Hi again!
I'm diving inside DirectUpdateHandler2 code and it seems that the problem
is that when a commit, when core.openNewSercher(true,true) is called it
returns a RefCounted with a new searcher reference that
points to an old (probably cached somehow) data dir. I've tried with
core.openNewSearc
I've seen that StandardDirectoryReader appears in the commit logs. Maybe
this DirectoryReader type is caching somehow the old segments in SolrB and
SolrC even if they have been commited previosly. If that's true, does exist
any other DirectoyReader type (I don't know, SimpleDirectoryReader or
FSDir
Hey guys,
I've doing some tests sharing the same index between three Solr servers:
*SolrA*: is allowed to both read and index. The index is stored in a NFS.
It has its own configuration files.
*SolrB and SolrC*: they can only read from the shared index and each one
has their own configuration fil
On 5/25/10 10:08 PM, Yao wrote:
My motivation is more from the performance prospective than functional
prospective. I was hoping by opening the Solr index/core read-only,
underlying Lucene IndexReader can be opened in read-only mode for optimum
query performance (removing the overhead of multi-t
message in context:
http://lucene.472066.n3.nabble.com/Solr-read-only-core-tp843049p843099.html
Sent from the Solr - User mailing list archive at Nabble.com.
ene.apache.org;
Subject: Solr read-only core
Is there a way to open a Solr index/core in read-only mode?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-read-only-core-tp843049p843049.html
Sent from the Solr - User mailing list archive at Nabble.com.
Is there a way to open a Solr index/core in read-only mode?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-read-only-core-tp843049p843049.html
Sent from the Solr - User mailing list archive at Nabble.com.
14 matches
Mail list logo
