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

Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/07/05 09:02:00 UTC

[jira] [Updated] (FLINK-28130) FLIP-224: Blocklist Mechanism

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

Martijn Visser updated FLINK-28130:
-----------------------------------
    Fix Version/s: 1.16.0

> FLIP-224: Blocklist Mechanism
> -----------------------------
>
>                 Key: FLINK-28130
>                 URL: https://issues.apache.org/jira/browse/FLINK-28130
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Coordination
>    Affects Versions: 1.16.0
>            Reporter: Lijie Wang
>            Assignee: Lijie Wang
>            Priority: Major
>             Fix For: 1.16.0
>
>
> In order to support speculative execution for batch jobs([FLIP-168|https://cwiki.apache.org/confluence/display/FLINK/FLIP-168%3A+Speculative+Execution+for+Batch+Job]), we need a mechanism to block resources on nodes where the slow tasks are located. We propose to introduce a blocklist mechanism as follows:  Once a node is marked as blocked, future slots should not be allocated from the blocked node, but the slots that are already allocated will not be affected.
> More details see [FLIP-224|https://cwiki.apache.org/confluence/display/FLINK/FLIP-224%3A+Blocklist+Mechanism]
> This is the umbrella ticket to track all the changes of this feature.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)