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

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2020/02/17 07:34:00 UTC

[jira] [Commented] (FLINK-16111) Kubernetes deployment does not respect "taskmanager.cpu.cores".

    [ https://issues.apache.org/jira/browse/FLINK-16111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038127#comment-17038127 ] 

Xintong Song commented on FLINK-16111:
--------------------------------------

cc [~fly_in_gis] [~azagrebin]

> Kubernetes deployment does not respect "taskmanager.cpu.cores".
> ---------------------------------------------------------------
>
>                 Key: FLINK-16111
>                 URL: https://issues.apache.org/jira/browse/FLINK-16111
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.10.0
>            Reporter: Xintong Song
>            Priority: Major
>             Fix For: 1.10.1, 1.11.0
>
>
> The Kubernetes deployment uses `kubernetes.taskmanager.cpu` for configuring TM cpu cores, and will fallback to number-of-slots if not specified.
> FLINK-14188 introduced a common option `taskmanager.cpu.cores` (ATM not exposed to users and for internal usage only). A common logic is to decide the TM cpu cores following the fallback order of "common option -> K8s/Yarn/Mesos specific option -> numberOfSlot".
> The above fallback rules are not respected by the Kubernetes deployment.



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