Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/595#issuecomment-93265798
Yes @hsaputra. One of the goals is to support resume/recovery of a job from
an intermediate result already produced. Another goal is to rework the deploy
logic of the `ExecutionGraph` to schedule tasks in a more optimal way instead
of merely deploying them from the source.
The changes in this pull request are a first step towards these goals. The
`scheduleUsingBacktracking` method backtracks from the sinks to the sources
while checking for available `IntermediateResultPartitions`. This can already
be used if you replace the `ScheduleMode` in `ExecutionGraph` to
`ScheduleMod.BACKTRACKING`. In a next commit, proper locking of the
intermediate results and resume will be supported.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
