* Freitag, 3. September 2021 08:09
> *To:* Alexis Sarda-Espinosa
> *Cc:* spoon_lz ; Denis Cosmin NUTIU <
> dnu...@bitdefender.com>; matth...@ververica.com; user@flink.apache.org
> *Subject:* Re: Deploying Flink on Kubernetes with fractional CPU and
> different limits and request
. September 2021 08:09
To: Alexis Sarda-Espinosa
Cc: spoon_lz ; Denis Cosmin NUTIU ;
matth...@ververica.com; user@flink.apache.org
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different
limits and requests
Hi Alexis
Thanks for your valuable inputs.
First, I want to share
OURCE_LIMIT_FACTOR_PREFIX *=
> *"kubernetes.jobmanager.limit-factor."*;
> *public static final *String
> *KUBERNETES_TASKMANAGER_RESOURCE_LIMIT_FACTOR_PREFIX *=
> *"kubernetes.taskmanager.limit-factor."*;
>
>
>
> BTW, we already have an o
; Alexis Sarda-Espinosa
; matth...@ververica.com;
user@flink.apache.org
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different
limits and requests
Hi Yang,
I agree with you, but I think the limit-factor should be greater than or equal
to 1, and default to 1 is a better
pod templates, right? Allowing more custom scenarios
without letting the configuration options get bloated.
Regards,
Alexis.
From: Denis Cosmin NUTIU
Sent: Donnerstag, 26. August 2021 15:55
To: matth...@ververica.com
Cc: user@flink.apache.org; danrtsey...@gmail.com
Subject: Re: Deploying
T_FACTOR_PREFIX =
>> "kubernetes.taskmanager.limit-factor.";
>>
>>
>> BTW, we already have an old ticket for this feature[1].
>>
>>
>> [1]. https://issues.apache.org/jira/browse/FLINK-15648
>>
>> Best,
>> Yang
>>
>> Alex
gust 31, 2021 6:04 AM
To: Alexis Sarda-Espinosa
Cc: Denis Cosmin NUTIU ; matth...@ververica.com
; user@flink.apache.org
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different
limits and requests
Hi all,
I think it is a good improvement to support different resource requ
nfiguration file only if the pod templates don’t specify any
> resources. That was the goal of supporting pod templates, right? Allowing
> more custom scenarios without letting the configuration options get bloated.
>
>
>
> Regards,
>
> Alexis.
>
>
>
> *From:* Denis Cos
t: Tuesday, August 31, 2021 6:04 AM
To: Alexis Sarda-Espinosa
Cc: Denis Cosmin NUTIU ; matth...@ververica.com
; user@flink.apache.org
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different
limits and requests
Hi all,
I think it is a good improvement to support different
com>;
matth...@ververica.com <matth...@ververica.com>;
user@flink.apache.org <user@flink.apache.org>
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different limits and requests
Hi all,
I think it is a good improvement to support different resource requests
: Denis Cosmin NUTIU mailto:dnu...@bitdefender.com>>
Sent: Donnerstag, 26. August 2021 15:55
To: matth...@ververica.com<mailto:matth...@ververica.com>
Cc: user@flink.apache.org<mailto:user@flink.apache.org>;
danrtsey...@gmail.com<mailto:danrtsey...@gmail.com>
Subject: Re: Deployi
--
> *From:* Yang Wang
> *Sent:* Tuesday, August 31, 2021 6:04 AM
> *To:* Alexis Sarda-Espinosa
> *Cc:* Denis Cosmin NUTIU ; matth...@ververica.com
> ; user@flink.apache.org
> *Subject:* Re: Deploying Flink on Kubernetes with fractional CPU and
> d
___
From: Yang Wang
Sent: Tuesday, August 31, 2021 6:04 AM
To: Alexis Sarda-Espinosa
Cc: Denis Cosmin NUTIU ; matth...@ververica.com
; user@flink.apache.org
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different
limits and requests
Hi all,
etting the configuration options get bloated.
>
>
>
> Regards,
>
> Alexis.
>
>
>
> *From:* Denis Cosmin NUTIU
> *Sent:* Donnerstag, 26. August 2021 15:55
> *To:* matth...@ververica.com
> *Cc:* user@flink.apache.org; danrtsey...@gmail.com
> *Subject:* Re: De
.
Regards,
Alexis.
From: Denis Cosmin NUTIU
Sent: Donnerstag, 26. August 2021 15:55
To: matth...@ververica.com
Cc: user@flink.apache.org; danrtsey...@gmail.com
Subject: Re: Deploying Flink on Kubernetes with fractional CPU and different
limits and requests
Hi Matthias,
Thanks for getting back to me
Hi Matthias,
Thanks for getting back to me and for your time!
We have some Flink jobs deployed on Kubernetes and running kubectl top pod
gives the following result:
NAMECPU(cores)
MEMORY(bytes)
aa-78c8cb77d4-zlmpg 8
Hi Denis,
I did a bit of digging: It looks like there is no way to specify them
independently. You can find documentation about pod templates for
TaskManager and JobManager [1]. But even there it states that for cpu and
memory, the resource specs are overwritten by the Flink configuration. The
code
17 matches
Mail list logo