You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2021/03/15 08:35:00 UTC

[jira] [Created] (FLINK-21793) Native K8s does not respect TM memory setups decided by RM

Xintong Song created FLINK-21793:
------------------------------------

             Summary: Native K8s does not respect TM memory setups decided by RM
                 Key: FLINK-21793
                 URL: https://issues.apache.org/jira/browse/FLINK-21793
             Project: Flink
          Issue Type: Bug
          Components: Deployment / Kubernetes
    Affects Versions: 1.13.0
            Reporter: Xintong Song
            Assignee: Xintong Song
             Fix For: 1.13.0


Currently, {{kubernetes-taskmanager.sh}} decides JVM options (Xmx, Xms, etc.) from a cluster-wised configuration overwritten by TM-specific dynamic properties. The problem is that, if the cluster-wised configuration contains some unwanted options, there's no way to remove/unset them via dynamic properties, which leads to inconsistent JVM options.

One of the key improvement of FLIP-49 was to make all memory calculations happen in one place, which is the RM side for active RM modes. According to this principle, I'd suggest to generate the memory related JVM options on RM side, and passing them to TM through ENVs.

This only affects fine-grained resource management.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)