search

WedjaaOpen / ElasticParser

ElasticParser
Apache License 2.0
3 stars 5 forks source link

connection (socket) still open #16

Open cpsgu opened 7 years ago

cpsgu commented 7 years ago

I call a subreport with following properties:

(Subreport has a different data source / data connection as main report).

Actually I have the problem, that the connection to ES Server will not be closed after report creation is done.

Is there some workaround or fix, that the connection will be closed? Please can somebody help me? Thank you

additional foundings: I analyzed the traffic (tcp connections) with wireshark. per subreport call, there will be opened around 15 tcp connection (with high ports up to arround 30) - only with one, the query will be send to ES. this connection will be closed but some connection (and threads) will stay and all 5 seconds they made a request to the ES "action = cluster/state". not more... Is there a way (config) to limit the open threads and tcp connection?

In my productive environment, there are ~15000 tcp connection opened permanently.

Thank you

cpsgu commented 7 years ago

Is someone from the developers ready to give me a help to this topic. I guess, it will be helpfull for the whole project. Thank you

Wedjaa commented 7 years ago

Will look into this. The traffic you are seeing is coming from the ES client talking to the cluster. We may need to kill the ES client once the report is done and spin up a new one or maybe manage a pool of clients.