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 2018/09/24 14:45:00 UTC

[jira] [Created] (FLINK-10411) Make ClusterEntrypoint more modular

Till Rohrmann created FLINK-10411:
-------------------------------------

             Summary: Make ClusterEntrypoint more modular
                 Key: FLINK-10411
                 URL: https://issues.apache.org/jira/browse/FLINK-10411
             Project: Flink
          Issue Type: Improvement
          Components: Distributed Coordination
    Affects Versions: 1.7.0
            Reporter: Till Rohrmann
            Assignee: Till Rohrmann
             Fix For: 1.7.0


Currently, the {{ClusterEntrypoint}} is not very modular in the sense that it cannot be really used for testing purposes (e.g. starting a {{Dispatcher}} with a {{WebMonitorRestEndpoint}}). The problem is that the {{ClusterEntrypoint}} combines too many responsibilities (creating the cluster services, starting the cluster components and deciding on when to terminate the JVM process).

I suggest to make the structure more compositional, meaning to split up the service generation from the cluster component start up. That way we could also remove code duplication between the different {{ClusterEntrypoint}} implementations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)