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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/29 15:26:00 UTC

[jira] [Updated] (FLINK-14280) Introduce DispatcherRunner for better separation of concerns

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

ASF GitHub Bot updated FLINK-14280:
-----------------------------------
    Labels: pull-request-available  (was: )

> Introduce DispatcherRunner for better separation of concerns
> ------------------------------------------------------------
>
>                 Key: FLINK-14280
>                 URL: https://issues.apache.org/jira/browse/FLINK-14280
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>
> In order to separate concerns (leader election, job recovery, other dispatcher work) which are currently all contained in the {{Dispatcher}}, I propose to add a {{DispatcherRunner}} interface which encapsulates how the {{Dispatcher}} is executed. The {{DispatcherRunner}} should be used by the {{DispatcherResourceManagerComponent}} instead of directly using the {{Dispatcher}}.



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