[jira] [Updated] (FLINK-18620) Unify behaviors of active resource managers

["Xintong Song (Jira)" <ji...@apache.org>]

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

Xintong Song updated FLINK-18620:
---------------------------------
    Fix Version/s: 1.12.0

> 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
>             Fix For: 1.12.0
>
>
> 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)