t;
> On Thu, Dec 7, 2023 at 9:32 AM richard.su wrote:
>
>> Hi Gyula, Flink version is 1.14
>> Our flink version is hard to upgrade since we have some user in our
>> platform.
>> sorry I have not noticed this configuration, it's confusing because flink
>> ope
gt;
> This is however only available in Flink 1.15 and above.
>
> Cheers,
> Gyula
>
> On Thu, Dec 7, 2023 at 9:15 AM richard.su wrote:
>
>> Hi, Community, I had found out this issue, but I'm not sure this issue
>> have any solution. I have tried flink operator 1.6
gt;
> This is however only available in Flink 1.15 and above.
>
> Cheers,
> Gyula
>
> On Thu, Dec 7, 2023 at 9:15 AM richard.su wrote:
>
>> Hi, Community, I had found out this issue, but I'm not sure this issue
>> have any solution. I have tried flink operator 1.6
of container when pod is missing and jm deployment is missing.
Thanks to your time to read this issue.
Richard Su
>
> 2023年12月6日 13:34，richard.su 写道：
>
> For more information to produce this problem,
>
> version: flink operator 1.4
> mode: native
> job: wordcount
jvm-overhead.fraction ? That
> would reserve more memory from the total process memory for non-JVM use.
>
> Gyula
>
> On Tue, Dec 5, 2023 at 1:50 PM richard.su wrote:
>
>> Sorry, "To be clear, we need a container has memory larger than request,
>> and confirm this p
Sorry, "To be clear, we need a container has memory larger than request, and
confirm this pod has Guarantee Qos." which need to be "To be clear, we need a
container has memory larger than process.size, and confirm this pod has
Guarantee Qos."
Thanks.
Richard Su
> 2023
ontainer for various
> purposes but these are all covered in detail by the flink memory configs.
>
> Cheers
> Gyula
>
> On Tue, Dec 5, 2023 at 1:06 PM richard.su wrote:
>
>> I think the new configuration could be :
>>
>> "kubernetes.taskmanager.memory.amo
t memory, but
using this configuration for decoupling logic.
Thanks
Richard Su
> 2023年12月5日 19:22，richard.su 写道：
>
> Hi, Gyula, from my opinion, this still will using flinkDeployment's resource
> filed to set jobManager.memory.process.size, and I have told an uncovered
> case t
This change can also help
>> with issues when users use Flink Kubernetes commands directly, without the
>> operator.
>>
>> Thanks
>> Surendra
>>
>>
>> On Tue, Dec 5, 2023 at 3:10 PM richard.su wrote:
>>
>>> Sorry Gyu
:13，richard.su 写道：
>
> Thank you for your time, Gyula, I have more question about Flink-33548, we
> can have more discussion about this and make progress:
>
> 1. I agree with you about declaring resources in FlinkDeployment resource
> sections. But Flink O
loyment resource sections. It's well documented and worked very
> well so far for most users.
> This is pretty common practice for kubernetes.
>
> Cheers,
> Gyula
>
> On Tue, Dec 5, 2023 at 9:35 AM richard.su wrote:
>
>> Hi, Gyula, is there had any progress in FLIN
Hi, Gyula, is there had any progress in FLINK-33548? I would like to join the
discussion but I haven't seen any discussion in the url.
I also make flinkdeployment by flink operator, which indeed will override the
process size by TaskmanagerSpec.resources or JobmanagerSpec.resources, which
12 matches
Mail list logo
