Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/595#issuecomment-97488698
I'm closing because I opened a new pull request #640.
---
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 p
Github user mxm closed the pull request at:
https://github.com/apache/flink/pull/595
---
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
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/595#issuecomment-93948227
@hsaputra You're welcome. Thanks for the additional feedback.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/595#discussion_r28579522
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/ExecutionGraph.java
---
@@ -412,28 +436,141 @@ public ScheduleMode getScheduleMode()
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/595#discussion_r28579554
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/Execution.java
---
@@ -851,6 +862,7 @@ private void sendUpdateTaskRpcCall(final Simp
Github user hsaputra commented on a diff in the pull request:
https://github.com/apache/flink/pull/595#discussion_r28570168
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/ExecutionGraph.java
---
@@ -412,28 +436,141 @@ public ScheduleMode getScheduleM
Github user hsaputra commented on a diff in the pull request:
https://github.com/apache/flink/pull/595#discussion_r28570539
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/Execution.java
---
@@ -851,6 +862,7 @@ private void sendUpdateTaskRpcCall(final
Github user hsaputra commented on the pull request:
https://github.com/apache/flink/pull/595#issuecomment-93798071
Thanks @mxm, appreciate the additional information about the PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
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 `Executi
Github user hsaputra commented on the pull request:
https://github.com/apache/flink/pull/595#issuecomment-93186180
@mxm could you add more information about this backtracking mode? Is this
to support recovery of failed job?
---
If your project is set up for it, you can reply to this
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/595#discussion_r28319765
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/taskmanager/TaskManager.scala
---
@@ -339,6 +339,12 @@ extends Actor with ActorLogMessages with Ac
Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/595#discussion_r28312964
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/taskmanager/TaskManager.scala
---
@@ -339,6 +339,12 @@ extends Actor with ActorLogMessages with Ac
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/595
[scheduling] implement backtracking with intermediate result checking
- backtracks from the sinks of an ExecutionGraph
- checks the availability of IntermediatePartitionResults
- marks ExecutionVe
13 matches
Mail list logo
