I remember a bug in EmbeddedSolrServer at 1.4.1 when exception bypasses request closing that lead to searcher leak and OOM. It was fixed about two years ago.
On Tue, Oct 2, 2012 at 1:48 PM, Robert Krüger <krue...@lesspain.de> wrote: > Hi, > > I'm using Solr 3.6.1 in an application embedded directly, i.e. via > EmbeddedSolrServer, not over an HTTP connection, which works > perfectly. Our application uses Thread.interrupt() for canceling > long-running tasks (e.g. through Future.cancel). A while (and a few > Solr versions) back a colleague of mine implemented a workaround > because he said that Solr didn't handle the thread's interrupted > status correctly, i.e. not setting the interrupted status after having > caught an InterruptedException or rethrowing it, thus killing the > information that an interrupt has been requested, which breaks > libraries relying on that. However, I did not find anything up-to-date > in mailing list or forum archives on the web. Is that still or was it > ever the case? What does one have to watch out for when interrupting a > thread that is doing anything within Solr/Lucene? > > Any advice would be appreciated. > > Regards, > > Robert > -- Sincerely yours Mikhail Khludnev Tech Lead Grid Dynamics <http://www.griddynamics.com> <mkhlud...@griddynamics.com>
