[
https://issues.apache.org/jira/browse/FLINK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945074#comment-14945074
]
ASF GitHub Bot commented on FLINK-2793:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1202#issuecomment-145868099
OK. I've addressed your comments in the last two commits. Thanks again!
- The associated local leader gateway is only resolved once and getGateway
will only return this one (new leader notifications don't change this one and
only affect the redirect address)
- The handlers don't block on the redirect address, but just read the
current redirect address.
> Redirect to leading JobManager web fronted in non-standalone mode
> -----------------------------------------------------------------
>
> Key: FLINK-2793
> URL: https://issues.apache.org/jira/browse/FLINK-2793
> Project: Flink
> Issue Type: Improvement
> Components: JobManager
> Affects Versions: 1.0
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> In case of a non-standalone recovery mode, the job manager frontend of
> non-leading job managers prints the job manager information of its associated
> job manager. Because the job manager is not leading, nothing shows up.
> The web frontend cannot directly communicate with the leading job manager,
> because many job manager structures like the execution graph are not
> serializable.
> A work around is to redirect to the web frontend of the leading job manager.
> This makes sure that all interesting information is presented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
