Re: Identify Reference Leak in Custom Code related to Solr

Hi Amrit, I suppose it is related to https://github.com/sematext/solr-researcher/issues/6 Can you please continue with conversation there, and one of us can update ML when issue is resolved in case there are others who could be interested in

Re: Identify Reference Leak in Custom Code related to Solr

Emir, Solr version: 6.6, SolrCloud We followed the instructions on README.md on the github project. Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 Medium: https://medium.com/@s

Re: Identify Reference Leak in Custom Code related to Solr

Hi Amrit, I’ll check with my colleague that worked on this. In the meantime, can you provide more info about setup: Solr version, M-S or cloud and steps that we can do to reproduce it. Thanks, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Supp

Identify Reference Leak in Custom Code related to Solr

Hi, We incorporated *https://github.com/sematext/solr-researcher * into our project and it is responsible for memory leak / reference leak which is causing multiple *SolrIndexSearcher *objects in the heap dump. 37 instances of *"org.apache.solr.search.