Re: Flink 1.10 container memory configuration with Mesos.

BTW, the dynamic config will also occur in TM side logs [1]. It would be good to print it in INFO level as well. [1] https://github.com/apache/flink/blob/663af45c7f403eb6724852915bf2078241927258/flink-mesos/src/main/java/org/apache/flink/mesos/entrypoint/MesosTaskExecutorRunner.java#L77 Best, Ya

Re: Flink 1.10 container memory configuration with Mesos.

It seems we already have such logs in [1]. If that is the case, +1 for changing it to INFO level. [1] https://github.com/apache/flink/blob/663af45c7f403eb6724852915bf2078241927258/flink-mesos/src/main/java/org/apache/flink/mesos/runtime/clusterframework/LaunchableMesosWorker.java#L341 Best, Yangz

Re: Flink 1.10 container memory configuration with Mesos.

Instead of just launching TM as it works right now, I suggest to log launch command first, and then launch TM

Re: Flink 1.10 container memory configuration with Mesos.

Glad to hear that your issue is fixed. I'm not sure what you suggest to add. Could you tell it more specific or create a Jira ticket? Best, Yangze Guo On Thu, Mar 12, 2020 at 3:51 PM Alexander Kasyanenko wrote: > > Hi Yangze, Xintong, > > Thank you for instant response. > > And big thanks for t

Re: Flink 1.10 container memory configuration with Mesos.

Hi Yangze, Xintong, Thank you for instant response. And big thanks for the hint on TM launch command. It indeed was the problem. I've added my own custom mesos-taskmanager.sh to echo the launch command (I've switched to DEBUG lev

Re: Flink 1.10 container memory configuration with Mesos.

Hi Alex, Could you try to check and post your TM launch command? I suspect that there might be some unrecognized arguments that prevent the rest of arguments being parsed. The TM memory configuration process works as follow: 1. The resource manager will parse the configurations, checking whic

Re: Flink 1.10 container memory configuration with Mesos.

Hi, Alexander I could not reproduce it in my local environment. Normally, Mesos RM will calculate all the mem config and add it to the launch command. Unfortunately, all the log I could found for this command is at the DEBUG level. Would you mind changing the log level to DEBUG or sharing anything

Flink 1.10 container memory configuration with Mesos.

Hi folks, I have a question related configuration for new memory introduced in flink 1.10. Has anyone encountered similar problem? I'm trying to make use of *taskmanager.memory.process.size* configuration key in combination with mesos session cluster, but I get an error like this: 2020-03-11 11:4