You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2025/03/10 15:29:00 UTC
[jira] [Created] (FLINK-37448) status.taskManager.replicas to show actual TaskManager count
Robert Metzger created FLINK-37448:
--------------------------------------
Summary: status.taskManager.replicas to show actual TaskManager count
Key: FLINK-37448
URL: https://issues.apache.org/jira/browse/FLINK-37448
Project: Flink
Issue Type: Improvement
Components: Kubernetes Operator
Reporter: Robert Metzger
According to the code and documentation, {{status.taskManager.replicas}} shows a calculated number of TaskManager replicas.
I've opened this ticket to discuss if it makes sense to show the actual TaskManager count instead.
We have that information already in the codebase: https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/service/AbstractFlinkService.java#L753
It shouldn't be too hard to expose that number as taskManager replicas in the status.
Would this qualify as a breaking change (because we are changing the semantics)?
The information in status.taskManager.replicas is not accurate when using standalone deployments with reactive mode -- in that case, the actual number of TaskManagers can change over time and is not determined by the config.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)