[
https://issues.apache.org/jira/browse/FLINK-28144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu closed FLINK-28144.
---------------------------
Fix Version/s: 1.16.0
Resolution: Done
Done via:
f2f83e1956eccecaa2371b21bddaf7778bb4f819
04f2f0c2660b312449419a3acb58a46a38d84f64
72ea8b5999bf36125aa5f1a38df4ec52c7a95702
387b2a473d0c0a8d58d1ca0401894dffc0527b31
> Let JobMaster support blocklist mechanism
> -----------------------------------------
>
> Key: FLINK-28144
> URL: https://issues.apache.org/jira/browse/FLINK-28144
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.16.0
> Reporter: Lijie Wang
> Assignee: Lijie Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> SlotPool should avoid allocating slots that located on blocked nodes. To do
> that, our core idea is to keep the SlotPool in such a state: there is no slot
> in SlotPool that is free (no task assigned) and located on blocked nodes.
> Details are as following:
> 1. When receiving slot offers from task managers located on blocked nodes,
> all offers should be rejected.
> 2. When a node is newly blocked, we should release all free(no task assigned)
> slots on it. We need to find all task managers on blocked nodes and release
> all free slots on them by SlotPoolService#releaseFreeSlotsOnTaskManager.
> 3. When a slot state changes from reserved(task assigned) to free(no task
> assigned), it will check whether the corresponding task manager is blocked.
> If yes, release the slot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
