You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/02/03 14:26:51 UTC

[jira] [Resolved] (FLINK-5499) Try to reuse the resource location of prior execution attempt in allocating slot

     [ https://issues.apache.org/jira/browse/FLINK-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen resolved FLINK-5499.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

Implemented in
2e107b1cfaa6e31fe478191c74aa25d53ab49943
and
b9ed4ff151c5d3a64be395c660160b5619e32c7f


> 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
>             Fix For: 1.3.0
>
>
> 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.15#6346)