Not what I meant the LotsOfCores stuff doesn't issue the core API unload
command, it's just shutting down the searcher, getting rid of the internal
config structures and the like.
Best,
Erick
On Mon, Aug 3, 2015 at 7:12 PM, Brian Hurt wrote:
> So unloading a core doesn't delete the data?
So unloading a core doesn't delete the data? That is good to know.
On Mon, Aug 3, 2015 at 6:22 PM, Erick Erickson
wrote:
> This doesn't work in SolrCloud, but it really sounds like "lots of
> cores" which is designed
> to keep the most recent N cores loaded and auto-unload older ones, see:
> ht
Some further information:
The main things use memory that I see from my heap dump are:
1. Arrays of org.apache.lucene.util.fst.FST$Arc classes- which mainly seem
to hold nulls. The ones of these I've investigated have been held by
org.apache.lucene.util.fst.FST objects, I have 38 cores open and
This doesn't work in SolrCloud, but it really sounds like "lots of
cores" which is designed
to keep the most recent N cores loaded and auto-unload older ones, see:
http://wiki.apache.org/solr/LotsOfCores
Best,
Erick
On Mon, Aug 3, 2015 at 4:57 PM, Brian Hurt wrote:
> Is there are an easy way for
Is there are an easy way for a client to tell Solr to close or release the
IndexSearcher and/or IndexWriter for a core?
I have a use case where we're creating a lot of cores with not that many
documents per zone (a few hundred to maybe 10's of thousands). Writes come
in batches, and reads also te
