zhuzhurk opened a new pull request, #20080:
URL: https://github.com/apache/flink/pull/20080
…executions for each execution vertex
## What is the purpose of the change
With speculative execution, tracking prior executions in an
EvictingBoundedList does not work. This is because when using
EvictingBoundedList relies on the assumption that the historical executions are
added in ascending order of attempt number successively. This is no longer true
if speculative execution is enabled. e.g. 3 speculative execution attempts #1,
#2, #3 are running concurrently, later #3 failed, and then #1 failed, and
execution attempt #2 keeps running.
The broken assumption may result in exceptions in REST, job archiving and so
on.
This PR introduces an ExecutionHistory to replace EvictingBoundedList. It
hosts the historical executions in a LinkedHashMap with a size bound. When the
map grows beyond the size bound, elements are dropped from the head of the map
(FIFO order).
## Brief change log
- *Introduced ExecutionHistory to replace EvictingBoundedList*
- *Reworked the usages*
- *Reworked the statements of prior executions to historical executions*
## Verifying this change
- *Added unit tests ExecutionHistoryTest*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (**yes** / no / don't
know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (**not applicable** / docs /
JavaDocs / not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
