_
> From: xiangyu feng
> Sent: Friday, December 29, 2023 20:20
> To: dev@flink.apache.org
> Subject: Re: [DISCUSS] FLIP-397: Add config options for administrator JVM
> options
>
> Hi Zhanghao,
>
> Thanks for driving this. +1 for the overall idea
: [DISCUSS] FLIP-397: Add config options for administrator JVM
options
Hi Zhanghao,
Thanks for driving this. +1 for the overall idea.
One minor question, do we need separate administrator JVM options for both
JobManager and TaskManager? Or just one administrator JVM option for all?
I'm afraid of 6 jvm
Hi Zhanghao,
Thanks for driving this. +1 for the overall idea.
One minor question, do we need separate administrator JVM options for both
JobManager and TaskManager? Or just one administrator JVM option for all?
I'm afraid of 6 jvm
+1 for this, we have met jobs that need to set GC policies different from
the default ones to improve performance. Separating the default and
user-set ones can help us better manage them.
Best,
Fang Yong
On Fri, Dec 22, 2023 at 9:18 PM Benchao Li wrote:
> +1 from my side,
>
> I also met some
Thanks everyone. I'll start voting after the New Year's holiday if there's no
further comment.
Best,
Zhanghao Chen
From: Benchao Li
Sent: Friday, December 22, 2023 21:18
To: dev@flink.apache.org
Subject: Re: [DISCUSS] FLIP-397: Add config options
+1 from my side,
I also met some scenarios that I wanted to set some JVM options by
default for all Flink jobs before, such as
'-XX:-DontCompileHugeMethods', without it, some generated big methods
won't be optimized in JVM C2 compiler, leading to poor performance.
Zhanghao Chen 于2023年11月27日周一
Hi devs,
I'd like to start a discussion on FLIP-397: Add config options for
administrator JVM options [1].
In production environments, users typically develop and operate their Flink
jobs through a managed platform. Users may need to add JVM options to their
Flink applications (e.g. to tune
