flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wangzhijiang999 <...@git.apache.org>
Subject [GitHub] flink pull request #3125: [FLINK-5499][JobManager]Reuse the resource locatio...
Date Mon, 16 Jan 2017 09:30:46 GMT
GitHub user wangzhijiang999 opened a pull request:


    [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:


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: 淘江 <taojiang.wzj@alibaba-inc.com>
Date:   2017-01-16T09:28:19Z

    [FLINK-5499][JobManager]Reuse the resource location of prior execution attempt in allocating


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 but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message