You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by JIAZHOU GAO <gj...@gmail.com> on 2025/02/14 00:14:03 UTC

Question about in-place rescaling support in Flink k8s operator

Hi,

I have a few questions on in-place rescaling support in Flink k8s operator.

1. Seems it is in the development roadmap
<https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/development/roadmap/>.
Is there a plan for developing it? Any discussion threads that I can follow?
2. I noticed that the standalone autoscaler
<https://github.com/apache/flink-kubernetes-operator/blob/44dd679a5952569a7ae36395202fdf609130fdef/flink-autoscaler-standalone/src/main/java/org/apache/flink/autoscaler/standalone/realizer/RescaleApiScalingRealizer.java#L117>
has
the logic to trigger in-place rescaling through rescale api. But it does
not check if the Flink cluster has some task slots resources to accommodate
that request. Is that right?  In other words, if it asks for more
parallelism than what the cluster current task slots can accommodate, the
rescale would not happen?
3. To automatically increase task slots resources in the cluster to
fulfill the in-place rescaling request who asks for more parallelism than
what the current available task slots, I would assume that Flink k8s
operator needs a way to somehow add more task manager Pods without invoking
the full job restart. Is that something we already support or to be
developed?

Thank you!
Jiazhou

Re: Question about in-place rescaling support in Flink k8s operator

Posted by gy...@gmail.com.
Hi!

  

In place scaling is only supported and works correctly with the native mode,
which is the default and recommended mode when using the k8s operator. With
native mode it works well.

  

I personally don’t have plans to work on the standalone mode or to add this
support. It’s a bit tricky as you said. If someone is interested in working on
this feature , then it may happen but it will depend on that :)

  

Cheers

Gyula

  

Sent from my iPhone

  

> On 14 Feb 2025, at 01:16, JIAZHOU GAO <gj...@gmail.com> wrote:  
>  
>

> 
>
> Hi,  
>  
> I have a few questions on in-place rescaling support in Flink k8s operator.  
>  
> 1\. Seems it is in the development
> [roadmap](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-
> main/docs/development/roadmap/). Is there a plan for developing it? Any
> discussion threads that I can follow?
>
> 2\. I noticed that the standalone
> [autoscaler](https://github.com/apache/flink-kubernetes-
> operator/blob/44dd679a5952569a7ae36395202fdf609130fdef/flink-autoscaler-
> standalone/src/main/java/org/apache/flink/autoscaler/standalone/realizer/RescaleApiScalingRealizer.java#L117)
> has the logic to trigger in-place rescaling through rescale api. But it does
> not check if the Flink cluster has some task slots resources to accommodate
> that request. Is that right?  In other words, if it asks for more
> parallelism than what the cluster current task slots can accommodate, the
> rescale would not happen?  
> 3\. To automatically increase task slots resources in the cluster to fulfill
> the in-place rescaling request who asks for more parallelism than what the
> current available task slots, I would assume that Flink k8s operator needs a
> way to somehow add more task manager Pods without invoking the full job
> restart. Is that something we already support or to be developed?
>
>  
>
>
> Thank you!  
> Jiazhou