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

Till Rohrmann resolved FLINK-16437.
-----------------------------------
    Resolution: Fixed

Fixed via

7286c5cf22bd50bac081ef05771f15b0067f0a37
5b735c07ae5f62f84d7f09343132b8914ba73d03
7089bd68f3efb8cd83fa1abb03295b36df5cdae1
92b30ed17446f719de3ae99be09418a867cb657d
9c5a1d185d1cd7f3b5a4b37f2489330dcfbad2ba
8f43063182ef880140231a7a06f9f8b9cc268386
d981c94477889298ed1cd8c208e1abcd9521cdf9
6b99a571e009f30876b15ec8b91cf86e15d3f573

> Make SlotManager allocate resource from ResourceManager at the worker 
> granularity.
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-16437
>                 URL: https://issues.apache.org/jira/browse/FLINK-16437
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Xintong Song
>            Assignee: Xintong Song
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> This is the first step of FLINK-14106, including all the major changes inside 
> SlotManager and changes to the RM/SM interfaces, except changes for metrics 
> and status.
> At the end of this step, SlotManager should allocate resource from 
> ResourceManager with a WorkerResourceSpec, instead of slot ResourceProfile. 
> At this step, the WorkerResourceSpec will not be used, and the active RMs 
> will always use `ActiveResourceManager#taskExecutorProcessSpec` for 
> requesting TMs. We will change that in subsequent steps.



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

Reply via email to