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

Posted to issues@flink.apache.org by "Zili Chen (Jira)" <ji...@apache.org> on 2019/09/27 19:20:00 UTC

[jira] [Commented] (FLINK-14252) Encapsulate Dispatcher services in DispatcherServices container

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

Zili Chen commented on FLINK-14252:
-----------------------------------

Make sense to me.

A more general issue related is that we can document the "pattern" how Flink wants to manage concepts of cluster components so that we don't loss context in the further and it can be fast referred to. If you approve I'm glad to draft an early version and start a discussion. The output could be a develop document in a proper location that can be looked up in our community.

> Encapsulate Dispatcher services in DispatcherServices container
> ---------------------------------------------------------------
>
>                 Key: FLINK-14252
>                 URL: https://issues.apache.org/jira/browse/FLINK-14252
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>
> The list of required dispatcher services has grown quite unwieldy. In order to more easily pass them through the chain of factories, I suggest to create a {{DispatcherServices}} container which contains all {{Dispatcher}} services.



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