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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/14 07:05:00 UTC

[jira] [Updated] (FLINK-27222) Execution history limit can lead to eviction of critical local-recovery information

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

ASF GitHub Bot updated FLINK-27222:
-----------------------------------
    Labels: pull-request-available  (was: )

> Execution history limit can lead to eviction of critical local-recovery information
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-27222
>                 URL: https://issues.apache.org/jira/browse/FLINK-27222
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.15.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0, 1.15.1
>
>
> Local recovery relies on knowing the allocation id of the last deployment. To that end we iterate over all previous execution attempts and use the last {{assignedAllocationID}}, if any.
> However, since the execution history is bounded (to, by default, 16 entries) this can lead this information being evicted.
> In other words, with the default configuration (history limit = 16, restart delay = 1s) local recovery can only kick if the TM is restarted within 16 seconds.
> We should decouple this information from the execution (history).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)