[
https://issues.apache.org/jira/browse/FLINK-27314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528597#comment-17528597
]
Yang Wang commented on FLINK-27314:
-----------------------------------
The biggest challenge we could not support "reactive mode + native K8s
integration" is that the flink-kubernetes-operator could not control the
TaskManager pod allocation. It is fully controlled by Flink ResourceManager in
native K8s integration.
> Support reactive mode for native Kubernetes integration in Flink Kubernetes
> Operator
> ------------------------------------------------------------------------------------
>
> Key: FLINK-27314
> URL: https://issues.apache.org/jira/browse/FLINK-27314
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Fuyao Li
> Priority: Major
>
> Generally, this task is a low priority task now.
> Flink has some system level Flink metrics, Flink kubernetes operator can
> detect these metrics and rescale automatically based checkpoint(similar to
> standalone reactive mode) and rescale policy configured by users.
> The rescale behavior can be based on CPU utilization or memory utilization.
> # Before rescaling, Flink operator should check whether the cluster has
> enough resources, if not, the rescaling will be aborted.
> # We can create a addition field to support this feature. The fields below
> is just a rough suggestion.
> {code:java}
> reactiveScaling:
> enabled: boolean
> scaleMetric: enum ["CPU", "MEM"]
> scaleDownThreshold:
> scaleUpThreshold:
> minimumLimit:
> maximumLimit:
> increasePolicy: <increase/decrease exponentially or linearly..>
> <some other timeout configuration...>{code}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
