[
https://issues.apache.org/jira/browse/FLINK-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402348#comment-15402348
]
ASF GitHub Bot commented on FLINK-4299:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2322
[FLINK-4299] show loss of job manager in Client
This prints a message when the leading JobManager changes after first
connecting to a JobManager. Further, it prints a message when a connection
to a JobManager has been established.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-4299
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2322.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 #2322
----
commit bcbbe52c0db15d30518c7e4d868950612d083dbf
Author: Maximilian Michels <[email protected]>
Date: 2016-08-01T16:15:56Z
[FLINK-4299] show loss of job manager in Client
This prints a message when the leading JobManager changes after first
connecting to a JobManager. Further, it prints a message when a connection
to a JobManager has been established.
----
> Show loss of job manager in Client
> ----------------------------------
>
> Key: FLINK-4299
> URL: https://issues.apache.org/jira/browse/FLINK-4299
> Project: Flink
> Issue Type: Improvement
> Components: Client
> Reporter: Ufuk Celebi
> Assignee: Maximilian Michels
> Fix For: 1.1.0
>
>
> If the client looses the connection to a job manager and the job recovers
> from this, the client will only print the job status as {{RUNNING}} again. It
> is hard to actually notice that something went wrong and a job manager was
> lost.
> {code}
> ...
> 08/01/2016 14:35:43 Flat Map -> Sink: Unnamed(8/8) switched to RUNNING
> 08/01/2016 14:35:43 Source: Custom Source(6/8) switched to RUNNING
> <------ EVERYTHING'S RUNNING ------>
> 08/01/2016 14:40:40 Job execution switched to status RUNNING <--- JOB
> MANAGER FAIL OVER
> 08/01/2016 14:40:40 Source: Custom Source(1/8) switched to SCHEDULED
> 08/01/2016 14:40:40 Source: Custom Source(1/8) switched to DEPLOYING
> 08/01/2016 14:40:40 Source: Custom Source(2/8) switched to SCHEDULED
> ...
> {code}
> After {{14:35:43}} everything is running and the client does not print any
> execution state updates. When the job manager fails, the job will be
> recovered and enter the running state again eventually (at 14:40:40), but the
> user might never notice this.
> I would like to improve on this by printing some messages about the state of
> the job manager connection. For example, between {{14:35:43}} and
> {{14:40:40}} it might say that the job manager connection was lost, a new one
> established, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
