[ 
https://issues.apache.org/jira/browse/FLINK-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065465#comment-15065465
 ] 

ASF GitHub Bot commented on FLINK-3185:
---------------------------------------

GitHub user uce opened a pull request:

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

    [FLINK-3185] [runtime, tests] Log error on failure during recovery

    A failure during job recovery was not logged by the future executing the 
recovery. This led a user to think that recovery was not happening at all.
    
    Furthermore, some log messages have been improved and a test was fixed, 
which was not failing, but only printing the stack trace on failures.

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

    $ git pull https://github.com/uce/flink 3185-silence_of_the_ha_lambs

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

    https://github.com/apache/flink/pull/1472.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 #1472
    
----
commit 698e4eb8dee63751a53b8202436b59479b25a344
Author: Ufuk Celebi <[email protected]>
Date:   2015-12-18T13:49:19Z

    [FLINK-3185] [tests] Don't swallow test failure Exception

commit c991fba6c6325efbb835c4f419b4204d8664a5a9
Author: Ufuk Celebi <[email protected]>
Date:   2015-12-16T23:06:17Z

    [FLINK-3185] [runtime, tests] Log error on failure during recovery

----


> Silent failure during job graph recovery
> ----------------------------------------
>
>                 Key: FLINK-3185
>                 URL: https://issues.apache.org/jira/browse/FLINK-3185
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Runtime
>    Affects Versions: 0.10.1
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 0.10.2
>
>
> If there is a failure during job graph recovery from ZooKeeper and the 
> configured state backend, there is no way of telling what happened, because 
> the operation happens in a future and does not log any exceptions.
> The user sees "Recovering all jobs" and after that no relevant log messages 
> follow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to