On Wed, Dec 4, 2013 at 6:36 PM, OSMAN Metin wrote:
> During this massive update, we have sometimes a peak of active threads
> exceeding the limit of 8192 process authorized for the user running the
> tomcat and zookeeper process.
> When this happens, every hardCommit is failing with an "OutOfMemor
I'd second the use of jstack to check your threads. Each request (be it a
search or update) will generate a request handler thread on the Solr side
(unless you've set the limits in the HttpShardHandlerFactory (solr.xml for
solr-wide faults and/or under the requestHandler in SolrConfig.xml), we
set
Hi Metin,
I think removing the softCommit=true parameter on the client side will
definitely help as NRT wasn't designed to re-open searchers after every
document. Try every 1 second (or even every few seconds), I doubt your users
will notice. To get an idea of what threads are running in your J
