Re: Flink 1.10 container memory configuration with Mesos.

2020-03-12 Thread Alexander Kasyanenko
ific > 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 the hint on TM launch com

Re: Flink 1.10 container memory configuration with Mesos.

2020-03-12 Thread Alexander Kasyanenko
t; 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 min

Flink 1.10 container memory configuration with Mesos.

2020-03-11 Thread Alexander Kasyanenko
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

ClosureCleanerLevel.RECURSIVE on flink 1.8.1 creates endless loop with jackson ObjectMapper field.

2019-07-10 Thread Alexander Kasyanenko
Hi everyone, Can you please explain if this is expected behaviour or not? My environment: I have a session cluster of flink 1.8.1 and a job written in scala. I'm submitting it to it with flink CLI, specifying the address of jobmanager. To submit a job I'm using CLI from 2 flink docker images flin