flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkrish86 <...@git.apache.org>
Subject [GitHub] flink pull request #2195: FLINK-3397 Failed streaming jobs should fall back ...
Date Mon, 04 Jul 2016 11:37:33 GMT
GitHub user ramkrish86 opened a pull request:


    FLINK-3397 Failed streaming jobs should fall back to the most recent

    Initial patch to see if this is what is intended out of the JIRA. Thought a PR could help
me in getting a better feedback. I tried to tweak and add a test case but I could not. I followed
what was done in SavePointITCase and particularly testRestoreFailure(). But am not able to
get a flow where there could be a checkpoint and also a save point because this test case
allows the notification to happen when the job is removed and that clears all the existing
savePoints. So when the test case restores it always goes with the savePoint. 

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

    $ git pull https://github.com/ramkrish86/flink FLINK-3397

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 #2195
commit 70e881fba6ab1964600b4fc932a8f7b683e2ff1e
Author: Ramkrishna <ramkrishna.s.vasudevan@intel.com>
Date:   2016-07-04T11:32:11Z

    FLINK-3397 Failed streaming jobs should fall back to the most recent
    checkpoint/savepoint (Ram)


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