[
https://issues.apache.org/jira/browse/FLINK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943675#comment-14943675
]
ASF GitHub Bot commented on FLINK-2793:
---------------------------------------
Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/1202#discussion_r41169911
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/jobmanager/JobManager.scala
---
@@ -1773,8 +1812,7 @@ object JobManager {
.asSubclass(classOf[WebMonitor])
val ctor: Constructor[_ <: WebMonitor] =
clazz.getConstructor(classOf[Configuration],
- classOf[LeaderRetrievalService],
- classOf[ActorSystem])
+ classOf[LeaderRetrievalService], classOf[ActorSystem])
--- End diff --
I was going for Kafkaesque... :D Just kidding, will change it.
> 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: master
> 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)
