[FLINK-10411] Make ClusterEntrypoint more modular

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.7.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available
• Assignee: Till Rohrmann
• Reporter: Till Rohrmann
• Created: 24/Sep/18 14:44
• Updated: 15/Mar/19 09:31
• Resolved: 28/Sep/18 09:44

Description

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.

Issue Links

• is related to: FLINK-11929 Remove unused transientBlobCache in ClusterEntrypoint
• links to: GitHub Pull Request #6743