[
https://issues.apache.org/jira/browse/FLINK-27222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522701#comment-17522701
]
Chesnay Schepler edited comment on FLINK-27222 at 4/15/22 7:21 AM:
-------------------------------------------------------------------
master: 07bab2f72add9ecdffd8ffa038b552797ff72579
1.15: 4727a20922bbab81faf4247a2a89e820ba122c60
was (Author: zentol):
master: 07bab2f72add9ecdffd8ffa038b552797ff72579
> 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)
