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

Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/02/21 03:59:00 UTC

[jira] [Resolved] (FLINK-16139) Co-location constraints are not reset on task recovery in DefaultScheduler

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

Zhu Zhu resolved FLINK-16139.
-----------------------------
    Resolution: Fixed

Fixed via:
master: 8c01397018f20865094dec8c37cf44279651a279
release-1.10: fd3e6e7dcaee213dee2e1fa1da997f55738c8aeb

> Co-location constraints are not reset on task recovery in DefaultScheduler
> --------------------------------------------------------------------------
>
>                 Key: FLINK-16139
>                 URL: https://issues.apache.org/jira/browse/FLINK-16139
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Zhu Zhu
>            Assignee: Zhu Zhu
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.10.1, 1.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The colocation constraints are not reset on task recovery, which may lead to task recovery failures when allocating slots.
> We should reset the colocation constraints before resetting vertices, just like what we do in the legacy scheduler.



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