[
https://issues.apache.org/jira/browse/FLINK-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890118#comment-15890118
]
ASF GitHub Bot commented on FLINK-5934:
---------------------------------------
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/3437
[FLINK-5934] Set the Scheduler in the ExecutionGraph via its constructor
Before the scheduler was set when calling
ExecutionGraph.scheduleForExecution(). This
has the disadvantage that the ExecutionGraph has not scheduler set if
something else
went wrong before the scheduleForExecution call. Consequently, the job will
be stuck
in a restart loop because the recovery will fail if there is no Scheduler
set. In
order to solve the problem, the Scheduler is not passed to the
ExecutionGraph when
it is created.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink fixExecutionGraphScheduler
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3437.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3437
----
commit 5858c8dc79546ccde68b99993a2695216452bacc
Author: Till Rohrmann <[email protected]>
Date: 2017-02-28T16:27:03Z
[FLINK-5938] Replace ExecutionContext by Executor in Scheduler
In order to remove the Scheduler's dependency on Scala's ExecutionContext
and
Akka's futures, this PR replaces the ExecutionContext by an Executor which
is
used to execute the concurrent handleNewSlot call.
commit cb0301e1c72dd15def6bef515ea754152be47145
Author: Till Rohrmann <[email protected]>
Date: 2017-02-28T14:20:47Z
[FLINK-5934] Set the Scheduler in the ExecutionGraph via its constructor
Before the scheduler was set when calling
ExecutionGraph.scheduleForExecution(). This
has the disadvantage that the ExecutionGraph has not scheduler set if
something else
went wrong before the scheduleForExecution call. Consequently, the job will
be stuck
in a restart loop because the recovery will fail if there is no Scheduler
set. In
order to solve the problem, the Scheduler is not passed to the
ExecutionGraph when
it is created.
----
> Scheduler in ExecutionGraph null if failure happens in
> ExecutionGraph.restoreLatestCheckpointedState
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-5934
> URL: https://issues.apache.org/jira/browse/FLINK-5934
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.2.0, 1.1.4, 1.3.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
>
> If {{ExecutionGraph.restoreLatestCheckpointedState}} fails with an exception,
> then all subsequent recoveries will fail because the {{scheduler}} has not
> been set in the {{ExecutionGraph}}.
> I propose to set the {{scheduler}} when the {{ExecutionGraph}} is created to
> avoid this problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
