[
https://issues.apache.org/jira/browse/FLINK-18620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164562#comment-17164562
]
Till Rohrmann commented on FLINK-18620:
---------------------------------------
Thanks a lot for creating the design and POC [~xintongsong]. I've given both a
pass and I think they look very good. They make the whole {{ResourceManager}}
abstraction more maintainable and evolvable. +1 for creating the subtasks
according to the implementation plan and then to move forward.
> Unify behaviors of active resource managers
> -------------------------------------------
>
> Key: FLINK-18620
> URL: https://issues.apache.org/jira/browse/FLINK-18620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Major
>
> Flink supports various deployment modes: standalone, Kubernetes, Yarn &
> Mesos. For each deployment mode, a resource manager is implemented for
> managing the resources.
> While StandaloneResourceManager is quite different from the others by not
> being able to dynamically request and release resources, the other three
> (KubernetesResourceManager, YarnResourceManager and MesosResourceManager)
> share many logics in common. These common logics are currently duplicately
> implemented by each of the active resource managers. Such duplication leads
> to extra maintaining overhead and amplifies stability risks.
> This ticket proposes a refactor design for the resource managers, with better
> abstraction deduplicating common logics implementations and minimizing the
> deployment specific behaviors.
> This proposal is a pure refactor effort. It does not intend to change any of
> the current resource management behaviors.
> A detailed design doc and a simplified proof-of-concept implementation for
> the Kubernetes deployment are linked to this ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
