GitHub user uce opened a pull request:

    https://github.com/apache/flink/pull/1720

    [FLINK-3390] [runtime, tests] Restore savepoint on ExecutionGraph restart

    Temporary work around to restore initial state on failure during recovery as
    required by a user. Will be superseded by FLINK-3397 with better handling of
    checkpoint and savepoint restoring.
    
    A failure during recovery resulted in restarting a job without its savepoint
    state. This temporary work around makes sure that if the savepoint 
coordinator
    ever restored a savepoint and there was no checkpoint after the savepoint,
    the savepoint state will be restored again.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/flink 3390-savepoint_retry

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1720.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 #1720
    
----
commit 2a33ea6dbb74ae518464aa60f65161ebb6a918ee
Author: Ufuk Celebi <[email protected]>
Date:   2016-02-26T11:46:07Z

    [FLINK-3390] [runtime, tests] Restore savepoint path on ExecutionGraph 
restart
    
    Temporary work around to restore initial state on failure during recovery as
    required by a user. Will be superseded by FLINK-3397 with better handling of
    checkpoint and savepoint restoring.
    
    A failure during recovery resulted in restarting a job without its savepoint
    state. This temporary work around makes sure that if the savepoint 
coordinator
    ever restored a savepoint and there was no checkpoint after the savepoint,
    the savepoint state will be restored again.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to