[
https://issues.apache.org/jira/browse/FLINK-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijiang Wang updated FLINK-5499:
---------------------------------
Description: 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. (was: 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.)
> 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
>
> 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)
