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 <bhur...@gmail.com> wrote: > 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 <erickerick...@gmail.com> > 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: >> http://wiki.apache.org/solr/LotsOfCores >> >> Best, >> Erick >> >> On Mon, Aug 3, 2015 at 4:57 PM, Brian Hurt <bhur...@gmail.com> wrote: >> > 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 tend to be bursty, if less so than the writes. >> > >> > And we're having problems with ram usage on the server. Poking around a >> > heap dump, the problem is that every IndexSearcher or IndexWriter being >> > opened is taking up large amounts of memory. >> > >> > I've looked at the unload call, and while it is unclear, it seems like it >> > deletes the data on disk as well. I don't want to delete the data on >> disk, >> > I just want to unload the searcher and writer, and free up the memory. >> > >> > So I'm wondering if there is a call I can make when I know or suspect >> that >> > the core isn't going to be used in the near future to release these >> objects >> > and return the memory? Or a configuration option I can set to do so >> after, >> > say, being idle for 5 seconds? It's OK for there to be a performance hit >> > the first time I reopen the core. >> > >> > Thanks, >> > >> > Brian >>
