Hi If your JM's container is killed by YARN due to beyond physical memory limit and your job's code is not changed but just bumped the Flink verion , I think you could use jmap command to dump the memory of your JobManager to see the difference between 1.4.2 and 1.5.2, and you could also open the GC log to see the difference.
In my experience, "jobmanager.execution.attempts-history-size" is configured too large, operator's name to too long for metrics stored in JM or even not configured checkpoint path (always return ByteStreamStateHandle back to JM) would impact the JM's memory footprint. Best Yun ________________________________ From: eSKa <eska...@gmail.com> Sent: Tuesday, September 25, 2018 14:45 To: user@flink.apache.org Subject: Re: JobManager container is running beyond physical memory limits anyone? -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
