unsubscribe
From: Srivatsan
Sent: Wednesday, April 23, 2014 2:58 PM
To: solr-user@lucene.apache.org
Subject: Re: Collection - loadOnStartup
Dear Rich Mayfield,
Sorry for late reply.
We didn't continue further in that. We have moved to Elastics
Dear Rich Mayfield,
Sorry for late reply.
We didn't continue further in that. We have moved to Elasticsearch.
Elasticsearch suits best for our case than Solr.
with regards
Ranjith Venkatesan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Collection-loadOnStartup-tp4082
You're right, we're basically working around inherent problems. SolrCloud and
large numbers of cores is not a combination that yields reliable restarts.
Even under the best of conditions - a completely silent (no updates, no
selects) environment - if I restart two nodes, each containing ~800
replic
I was actually going to try orchestrating SolrCloud restart myself using
loadOnStartup="false".
Did you pursue this any further?
With Solr 4.7.1...
I found that using core LOAD, RELOAD, and CREATE do not take a "down"
replica to "active". What I've found so far is that I can startup a
collection
I would _really_ advise you avoid trying this without an absolutely
compelling, _demonstrated_ need.
Unless you have a _lot_ of cores, the load time
for even 100 or so isn't horrible, so if you're noticing a
significant lag time, it's probably worth looking at why that is before
jumping into using
I started looking in reducing the time taken to load cores during cluster
restart. For initializing the core, building config file takes considerable
amount of time. In our case, schema remains same for all collections(cores)
. Hence it can be kept static, and avoid loading time.
In the mean whil
Frankly, you're into somewhat uncharted waters, the whole lazy core
capability was designed for non-cloud mode.
Cores are initialized when the first request comes in that addresses
the core. Whether ZK and SolrCloud know a core is active before
the first time it's loaded I don't know.
I think you
Hi
I manually edited core.properties file by setting /loadOnStartup=false/ on
all cores. But here i am facing a problem. After starting the solr cloud
servers, I couldnt index to any collection till particular interval. I am
getting exception like "No Live Solr Servers".
=> If we submit a index re
Thanks Erick
--
View this message in context:
http://lucene.472066.n3.nabble.com/Collection-loadOnStartup-tp4082531p4082938.html
Sent from the Solr - User mailing list archive at Nabble.com.
I don't think you can, really. Collections, at this point, is more
geared towards SolrCloud. The idea of lazy loading
matched with SolrCloud makes my head hurt.
I'm afraid for the nonce you'll have to individually edit the
solr.xml or core.properties files on the nodes once the
collections are cre
Then if so, how to set loadOnStartup for collectionsAPI in solr4.4 ???
--
View this message in context:
http://lucene.472066.n3.nabble.com/Collection-loadOnStartup-tp4082531p4082731.html
Sent from the Solr - User mailing list archive at Nabble.com.
For Solr 4.3.0, I don't think you can pass loadOnStartup to the Collections
API, although the Cores API accepts it. That's been my experience anyway.
On Mon, Aug 5, 2013 at 6:27 AM, Srivatsan wrote:
> No errors in zookeeper and solr. I m using CloudSolrServer for creating
> collections as said
No errors in zookeeper and solr. I m using CloudSolrServer for creating
collections as said above.I just want to set loadOnStartup to false for
cores in solr.xml. I dont want all cores to loadonstartup. Hence when
creating collection, i m trying to set this parameter to false. But still i
m gettin
You haven't given us much information to go on. _how_ does it fail?
What do the logs show? Any error returned? What is the response from
the server? Is zookeeper showing any problems?
Best
Erick
On Mon, Aug 5, 2013 at 7:01 AM, Srivatsan wrote:
> Hi,
>
> I am using solr -4.3.0 for my search appl
14 matches
Mail list logo
