Hi Sendoh, are you running batch or streaming jobs? In batch mode, workers allocate managed memory lazily by default. Memory is allocated up to the configured amount and never returned until Flink is shutdown. So, this would not indicate a memory leak.
Best, Fabian 2017-05-15 18:01 GMT+02:00 Sendoh <unicorn.bana...@gmail.com>: > Hi Flink users, > > How does memory usage percentage changes when starting the first job, > second > job and cancel a job which all use the same jar? > > I found that when starting the first job, it uses much more memory than the > second job. > The first job uses around 20 % and the second one may use only 5%. > > When canceling one of the jobs, the memory usage doesn't decrease. It means > GC is not triggered immediately? But even after 1 day the memory is not > released. > > My doubt is from we have a usecase which I wonder this has memory leak. I'm > not sure the memory is not released due to the job itself, or sth else. > > Best, > > Sendoh > > > > -- > View this message in context: http://apache-flink-user- > mailing-list-archive.2336050.n4.nabble.com/memory-usage-in- > task-manager-when-run-and-cancel-a-job-tp13142.html > Sent from the Apache Flink User Mailing List archive. mailing list archive > at Nabble.com. >
