[
https://issues.apache.org/jira/browse/FLINK-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016733#comment-16016733
]
ASF GitHub Bot commented on FLINK-6379:
---------------------------------------
Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/3942
This is a fairly straightforward port of the RM code to the FLIP-6
architecture.
Follow-ups to occur in future PRs include:
- adding support for releasing the worker
- compensating for the loss of a worker (beyond state cleanup)
- eliminating the use of `RegisteredMesosWorkerNode`
> Implement FLIP-6 Mesos Resource Manager
> ---------------------------------------
>
> Key: FLINK-6379
> URL: https://issues.apache.org/jira/browse/FLINK-6379
> Project: Flink
> Issue Type: Sub-task
> Components: Mesos
> Reporter: Eron Wright
> Assignee: Eron Wright
>
> Given the new ResourceManager of FLIP-6, implement a new
> MesosResourceManager.
> The minimal effort would be to implement a new resource manager while
> continuing to use the various local actors (launch coordinator, task monitor,
> etc.) which implement the various FSMs associated with Mesos scheduling.
> The Fenzo library would continue to solve the packing problem of matching
> resource offers to slot requests.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
