How many instances does MAT show for ElasticSearchConnection? A "leak suspect" is the class whose number of instances is the largest. It doesn't mean there's an actual memory leak.
Karl On Mon, Sep 17, 2018 at 7:49 AM Gustavo Beneitez <[email protected]> wrote: > Hi Karl, > > I reviewed the UI and there are a total of > ElasticSearch 100 > Seems not so many connections... > > > > El lun., 17 sept. 2018 a las 12:56, Karl Wright (<[email protected]>) > escribió: > > > Hi Gustavo, > > > > Connector instances are pooled in general, so once a connector instance > is > > created it is kept around. The number of instances will max out at the > > number of connections you allow in the UI when defining the connection. > > How many did you allocate? > > > > Karl > > > > > > On Mon, Sep 17, 2018 at 6:23 AM Gustavo Beneitez < > > [email protected]> > > wrote: > > > > > Hi there, > > > > > > I was indexing in production several intranet websites and I realized > the > > > performance was becoming poor (no tomcat restart for two weeks). > > > > > > After a few thoughts about what is going on I decided to create a dump > > > file and review it with eclipse MAT and I observed that the class > > > > > > Leak Suspects > > > > > > *org.apache.manifoldcf.agents.output.elasticsearch.ElasticSearchConnection* > > > > > > had a lot of instances and was growing up and never released. Do you > have > > > any issue related to Elastic? Maybe there is something related to our > > > version (2.4.6) of Elastic. > > > > > > I also have attached the MAT report. We have all components "by > default", > > > i.e. neither no customization of any component nor any new one created. > > > > > > Thanks in advance. > > > > > >
