You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/05/16 12:37:00 UTC

[jira] [Resolved] (FLINK-17248) Make the thread nums of io executor of ClusterEntrypoint and MiniCluster configurable

     [ https://issues.apache.org/jira/browse/FLINK-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann resolved FLINK-17248.
-----------------------------------
    Fix Version/s: 1.10.2
                   1.11.0
       Resolution: Fixed

Fixed via 

1.11.0: 367c613c63d922643b9e4d80c8f2913d43b72401
1.10.2: e3a95025fd7e01922a34cd78eeb858836382e425

> Make the thread nums of io executor of ClusterEntrypoint and MiniCluster configurable
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-17248
>                 URL: https://issues.apache.org/jira/browse/FLINK-17248
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Checkpointing, Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Yun Tang
>            Assignee: Yun Tang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0, 1.10.2
>
>
> FLINK-11851 introduce dedicated io executor for ClusterEntrypoint and MiniCluster with the the thread num as the cpu cores. However, this could introduce extra regression as we might use fewer threads compared with akka service before, e.g.FLINK-17073 . However, we cannot configure the thread num of the io executor to avoid such regression.
> One idea is to introduce such configuration to make the thread nums of io executor of ClusterEntrypoint and MiniCluster configurable.



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