flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] StefanRRichter opened a new pull request #6500: [FLINK-10066] Keep only archived version of previous executions
Date Mon, 06 Aug 2018 08:18:10 GMT
StefanRRichter opened a new pull request #6500: [FLINK-10066] Keep only archived version of
previous executions
URL: https://github.com/apache/flink/pull/6500
   ## What is the purpose of the change
   Currently, the execution vertex stores a limited amount of previous executions in a bounded
list. This happens primarily for archiving purposes and to remember previous locations and
allocation ids. We remember the whole execution to eventually convert it into an archived
   This seems unnecessary and dangerous as we have observed that this strategy is prone to
memory leaks in the job manager. With a very high vertex count or parallelism, remembering
complete executions can become very memory intensive. Instead I suggest to eagerly transform
the executions into the archived version before adding them to the list, i.e. only the archived
version is ever still referenced after the execution becomes obsolete. This gives better control
over which information about the execution should really be kept in memory.
   ## Brief change log
   Convert `Execution` directly to `ArchivedExecution` before remembering it in the bounded
list. I added the `AttemptID` to `ArchivedExecution` so that we can still support all previous
   ## Verifying this change
   This change is a trivial rework / code cleanup without any test coverage.
   ## Does this pull request potentially affect one of the following parts:
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (no)
   ## Documentation
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message