回复：回复：Flink job failing due to "Container is running beyond physical memory limits" error.

-- 发件人：Flink Developer 发送时间：2018年11月26日(星期一) 16:37 收件人：Flink Developer 抄　送：zhijiang ; user ; Gagan Agrawal 主　题：Re: 回复：Flink job failing due to "Container is running beyond physical memory limits" error. Also, after the Flink job has failed from the above error, the Flink job is

Re: 回复：Flink job failing due to "Container is running beyond physical memory limits" error.

Also, after the Flink job has failed from the above error, the Flink job is unable to recover from previous checkpoint. Is this the expected behavior? How can the job be recovered successfully from this? ‐‐‐ Original Message ‐‐‐ On Monday, November 26, 2018 12:35 AM, Flink Developer wr

Re: 回复：Flink job failing due to "Container is running beyond physical memory limits" error.

I am also experiencing this error message "Container is running beyond physical memory limits". In my case, I am using Flink 1.5.2 with 10 task managers, with 40 slots for each task manager. The memory assigned during flink cluster creation is 1024MB per task manager. The checkpoint is using Roc

回复：Flink job failing due to "Container is running beyond physical memory limits" error.

I think it is probably related with rockdb memory usage if you have not found OutOfMemory issue before. There already existed a jira ticket [1] for fixing this issue, and you can watch it for updates. :) [1] https://issues.apache.org/jira/browse/FLINK-10884 Best, Zhijiang -