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/08/24 12:17:00 UTC
[jira] [Commented] (FLINK-19037) Introduce proper IO executor in
Dispatcher
[ https://issues.apache.org/jira/browse/FLINK-19037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183195#comment-17183195 ]
Till Rohrmann commented on FLINK-19037:
---------------------------------------
The same actually applies for the {{ResourceManager}} as well. One idea could be to forward the {{ClusterEntrypoint.ioExecutor}} to the {{DispatcherResourceManagerComponent}} and then farther to the {{Dispatcher}} and {{ResourceManager}}.
> Introduce proper IO executor in Dispatcher
> ------------------------------------------
>
> Key: FLINK-19037
> URL: https://issues.apache.org/jira/browse/FLINK-19037
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Priority: Major
>
> Currently, IO operations in the {{Dispatcher}} are scheduled on the {{rpcService.getExecutor()}}.
> We should introduce a separate executor for IO operations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)