[
https://issues.apache.org/jira/browse/FLINK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945143#comment-14945143
]
ASF GitHub Bot commented on FLINK-2793:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1202#issuecomment-145885023
It's not superficial at all. It's cleaner, because the retriever is
independent of the redirect logic then.
I've decided against it though in order to keep the handlers cleaner (there
only two different kinds atm though, so it would be OK to add it) and because
the associated job manager URL is only known after start() is called, so I
would have to update all handlers lazily after that.
This is due to the start up ordering of
1. start web server (bind to port)
2. get web server port and start job manager with web server port configured
3. set job manager address at web server
This ordering allows both components to pick random ports.
I just didn't want to change too much code this at this point, because I
genuinely hope that we will make the execution graph serialisable after the
release and get back to the old solution. But I'm also happy to change it if
you like. Just ping me.
> 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)
