flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-10411) Make ClusterEntrypoint more modular
Date Fri, 28 Sep 2018 09:45:00 GMT

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

Till Rohrmann closed FLINK-10411.
---------------------------------
    Resolution: Fixed

Fixed via
1fcbc9f816460b1a159fd79b4c9bcf83327d79c3
b9ebf421c8979d99f2ae960075b76796ba0b6ac4
54c1b19181408ab280fd3d41c2d83a557e27a519
9f5fd073bd128006571c9e788c87938125fef52d

> 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
>            Priority: Minor
>              Labels: pull-request-available
>             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)

Mime
View raw message