Flink Application cluster/standalone job: some JVM Options added to Program Arguments

2021-01-15 Thread Alexey Trenikhun
Hello, I was trying to deploy Flink 1.12.0 Application cluster on k8s, I have following job manager arguments: standalone-job --job-classname com.x.App --job-id @/opt/flink/conf/fsp.conf However, when I print args from App.main(): [@/opt/flink/conf/ssp.conf, -D,

Re: Flink Application cluster/standalone job: some JVM Options added to Program Arguments

2021-01-17 Thread Matthias Pohl
Hi Alexey, thanks for reaching out to the Flink community. I'm not 100% sure whether you have an actual issue or whether it's just the changed behavior you are confused about. The change you're describing was introduced in Flink 1.12 as part of the work on FLIP-104 [1] exposing the actual memory us

Re: Flink Application cluster/standalone job: some JVM Options added to Program Arguments

2021-01-18 Thread Alexey Trenikhun
JOB args? Thanks, Alexey From: Matthias Pohl Sent: Sunday, January 17, 2021 11:53:29 PM To: Alexey Trenikhun Cc: Flink User Mail List Subject: Re: Flink Application cluster/standalone job: some JVM Options added to Program Arguments Hi Alexey, thanks for

Re: Flink Application cluster/standalone job: some JVM Options added to Program Arguments

2021-01-19 Thread Matthias Pohl
*To:* Alexey Trenikhun > *Cc:* Flink User Mail List > *Subject:* Re: Flink Application cluster/standalone job: some JVM Options > added to Program Arguments > > Hi Alexey, > thanks for reaching out to the Flink community. I'm not 100% sure whether > you have an actual issue