[ 
https://issues.apache.org/jira/browse/FLINK-14187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150682#comment-17150682
 ] 

Xintong Song commented on FLINK-14187:
--------------------------------------

Hi [~Anglenet],

Thanks for being interested on this thread. FLIP-56 is still on the agenda. 
Your contribution will be appreciated.

I would like to first share some latest updates on this thread, since the 
implementation plan for this FLIP has changed.
* Given that slot allocation is the one of the very core behaviors affecting 
Flink's all use cases, we found it a bit aggressive to completely replace the 
previous static slot allocation with the new dynamic slot allocation. We 
decided to keep both static and dynamic slot allocation, for the users to 
choose.
* In order to have multiple slot allocation strategies, we suspended this 
ticket and worked on FLINK-14106 first. The latter adjusted the boundaries 
between SlotManager and ResourceManager, and made SlotManager pluggable. In 
this way, each slot allocation strategy can be a separate SlotManager 
implementation.
* Given FLINK-14106, the subtasks of this ticket also need update.
** For step 3 & 4, instead of extending the current SlotManager, we are going 
to implement new SlotManagers for dynamic slot allocation.
** Step 5 should be introducing a configuration option for switching between 
different SlotManagers.
** Step 7 is probably not needed.

Based on the above current status, if you would like to, you may help on the 
following tasks.
* FLINK-16442, which is a subtask of FLINK-14106. This is the last missing 
piece of making slot allocation pluggable, which would unblock dynamic slot 
allocation on the Mesos deployment.
* FLINK-14190 & FLINK-14191 (step 3 & 4 of this ticket). Basically, these two 
tickets together implement a new SlotManager.

Please be aware that, whichever task you pick, it is important to first share, 
discuss and get consensus on your plan (what changes to make). The Apache Flink 
community suggests reaching consensus and getting assigned by a committer 
before working on the implementation. Please also take a look at the community 
[guides for contributing 
codes|https://flink.apache.org/contributing/contribute-code.html].

> FLIP-56 Dynamic Slot Allocation
> -------------------------------
>
>                 Key: FLINK-14187
>                 URL: https://issues.apache.org/jira/browse/FLINK-14187
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Coordination
>    Affects Versions: 1.9.0
>            Reporter: Xintong Song
>            Assignee: Xintong Song
>            Priority: Major
>              Labels: Umbrella
>             Fix For: 1.12.0
>
>
> This is the umbrella issue for 'FLIP-56: Dynamic Slot Allocation'.



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

Reply via email to