flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1984) Integrate Flink with Apache Mesos
Date Thu, 18 Aug 2016 13:26:20 GMT

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

ASF GitHub Bot commented on FLINK-1984:

Github user mxm commented on the issue:

    Thank you for your work @EronWright.  Finally could go through the code. All in all, very
impressive as the first step of the Mesos integration! I think this PR is in a mergeable state
if some minor comments are addressed.
    I'm not 100 % sure about all the additional actors yet. It seems like `ReconciliationCoordinator`,
`ConnectionMonitor`, `TaskMonitor` could also easily be handled inside `MesosFlinkResourceManager`.
In terms of modularity, I can see that having these run independently can give us a more flexible
setup. Which of the actors do you plan to re-use in the next set of changes? Clearly, in terms
of testability it comes in really handy. 

> Integrate Flink with Apache Mesos
> ---------------------------------
>                 Key: FLINK-1984
>                 URL: https://issues.apache.org/jira/browse/FLINK-1984
>             Project: Flink
>          Issue Type: New Feature
>          Components: Cluster Management
>            Reporter: Robert Metzger
>            Assignee: Eron Wright 
>            Priority: Minor
>         Attachments: 251.patch
> There are some users asking for an integration of Flink into Mesos.
> -There also is a pending pull request for adding Mesos support for Flink-: https://github.com/apache/flink/pull/251
> Update (May '16):  a new effort is now underway, building on the recent ResourceManager
> Design document:  ([google doc|https://docs.google.com/document/d/1WItafBmGbjlaBbP8Of5PAFOH9GUJQxf5S4hjEuPchuU/edit?usp=sharing])

This message was sent by Atlassian JIRA

View raw message