You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2019/12/04 16:19:00 UTC

[jira] [Closed] (FLINK-12761) Fine grained resource management

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

Xintong Song closed FLINK-12761.
--------------------------------
    Resolution: Duplicate

The remaining tasks of this proposal is separated into FLIP-49, FLIP-53, FLIP-56 and other follow-ups.

> Fine grained resource management
> --------------------------------
>
>                 Key: FLINK-12761
>                 URL: https://issues.apache.org/jira/browse/FLINK-12761
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.8.0, 1.9.0
>            Reporter: Xintong Song
>            Assignee: Xintong Song
>            Priority: Major
>              Labels: Umbrella, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This is an umbrella issue for enabling fine grained resource management in Flink.
> Fine grained resource management is a big topic that requires long term efforts. There are many issues to be addressed and designing decisions to be made, some of which may not be resolved in short time. Here we propose our design and implementation plan for the upcoming release 1.9, as well as our thoughts and ideas on the long term road map on this topic.
> A practical short term target is to enable fine grained resource management for batch sql jobs only in the upcoming Flink 1.9. This is necessary for batch operators added from blink to achieve good performance.
> Please find detailed design and implementation plan in attached docs. Any comment and feedback are welcomed and appreciated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)