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

Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2020/10/19 07:11:00 UTC

[jira] [Comment Edited] (FLINK-19700) Make Kubernetes Client in KubernetesResourceManagerDriver use io executor

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

Nicholas Jiang edited comment on FLINK-19700 at 10/19/20, 7:10 AM:
-------------------------------------------------------------------

Hi [~fly_in_gis], the point you mentioned is that KubernetesResourceManagerDriver uses getIoExecutor method to get io executor to replace the mainThreadExecutor?


was (Author: nicholasjiang):
[~fly_in_gis], do you mean that KubernetesResourceManagerDriver uses getIoExecutor method to get io executor to replace the mainThreadExecutor?

> Make Kubernetes Client in KubernetesResourceManagerDriver use io executor
> -------------------------------------------------------------------------
>
>                 Key: FLINK-19700
>                 URL: https://issues.apache.org/jira/browse/FLINK-19700
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>            Reporter: Yang Wang
>            Priority: Major
>             Fix For: 1.12.0
>
>
> Currently, the Kubernetes Client in {{KubernetesResourceManagerDriver}} is using a dedicated thread pool. After FLINK-19037 and FLINK-18722, we could get the io executor in {{KubernetesResourceManagerDriver}} and eliminate the redundant thread pool.



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