Hi, Thanks for analyzing the problem. If it turns out that there is a problem with the termination of the Kafka sources, could you please open an issue for that with your results?
Best, Stefan > On 11. Dec 2018, at 19:04, PedroMrChaves <pedro.mr.cha...@gmail.com> wrote: > > Hello Stefan, > > Thank you for the reply. > > I've taken a heap dump from a development cluster using jmap and analysed > it. To do the tests we restarted the cluster and then left a job running for > a few minutes. After that, we restarted the job a couple of times and > stopped it. After leaving the cluster with no running jobs for 20 min we > toke a heap dump. > > We've found out that a thread which consumes data from kafka was still > running with a lot of finalizer calls as depicted bellow. > > > <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/file/t612/Screenshot_2018-12-11_at_17.png> > > > I will deploy a job without a Kafka consumer to see if the code cache still > increases (all of our cluster have problems with the code cache, > coincidentally all of the deployed jobs read from kafka). > > > Best Regards, > Pedro Chaves > > > > ----- > Best Regards, > Pedro Chaves > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
