[
https://issues.apache.org/jira/browse/FLINK-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823681#comment-15823681
]
ASF GitHub Bot commented on FLINK-5499:
---------------------------------------
GitHub user wangzhijiang999 opened a pull request:
https://github.com/apache/flink/pull/3125
[FLINK-5499][JobManager]Reuse the resource location of prior executio…
Currently when schedule execution to request to allocate slot from
**SlotPool**, the **TaskManagerLocation** parameter is empty collection. So for
task fail over scenario, the new execution attempt may be deployed to different
task managers. If setting rockDB as state backend, the performance is better if
the data can be restored from local machine. So we try to reuse the
**TaskManagerLocation** of prior execution attempt when allocating slot from
**SlotPool**. If the **TaskManagerLocation** is empty from prior executions,
the behavior is the same with current status.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wangzhijiang999/flink FLINK-5499
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3125.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 #3125
----
commit ab2e24ae7e82be45359f249670f72664226ec18c
Author: 淘江 <[email protected]>
Date: 2017-01-16T09:28:19Z
[FLINK-5499][JobManager]Reuse the resource location of prior execution
attempt in allocating slot
----
> Try to reuse the resource location of prior execution attempt in allocating
> slot
> --------------------------------------------------------------------------------
>
> Key: FLINK-5499
> URL: https://issues.apache.org/jira/browse/FLINK-5499
> Project: Flink
> Issue Type: Improvement
> Components: JobManager
> Reporter: Zhijiang Wang
> Assignee: Zhijiang Wang
>
> Currently when schedule execution to request to allocate slot from
> {{SlotPool}}, the {{TaskManagerLocation}} parameter is empty collection. So
> for task fail over scenario, the new execution attempt may be deployed to
> different task managers. If setting rockDB as state backend, the performance
> is better if the data can be restored from local machine. So we try to reuse
> the {{TaskManagerLocation}} of prior execution attempt when allocating slot
> from {{SlotPool}}. If the {{TaskManagerLocation}} is empty from prior
> executions, the behavior is the same with current status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
