manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gustavo Beneitez <gustavo.benei...@gmail.com>
Subject Re: High performance issues with Elastic Connector
Date Mon, 17 Sep 2018 11:49:42 GMT
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 (<daddywri@gmail.com>)
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 <
> gustavo.beneitez@gmail.com>
> 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.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message