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

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_r41169783
  
    --- Diff: 
flink-runtime-web/src/main/java/org/apache/flink/runtime/webmonitor/JobManagerArchiveRetriever.java
 ---
    @@ -70,28 +104,68 @@ public ActorGateway getArchiveGateway() {
                return archiveGateway;
        }
     
    +   /**
    +    * Returns the current redirect address or <code>null</code> if the job 
manager associated with
    +    * this web monitor is leading. In that case, work with the gateway 
directly.
    +    */
    +   public String getRedirectAddress() {
    +           return redirectWebMonitorAddress;
    +   }
     
        @Override
        public void notifyLeaderAddress(String leaderAddress, UUID 
leaderSessionID) {
                if (leaderAddress != null && !leaderAddress.equals("")) {
                        try {
    -                           ActorRef jobManager = AkkaUtils.getActorRef(
    -                                           leaderAddress,
    -                                           actorSystem,
    +                           ActorRef jobManager = 
AkkaUtils.getActorRef(leaderAddress, actorSystem,
    --- End diff --
    
    Good catch


> 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)

Reply via email to