flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2793) Redirect to leading JobManager web fronted in non-standalone mode
Date Tue, 06 Oct 2015 08:25:26 GMT

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

ASF GitHub Bot commented on FLINK-2793:

Github user tillrohrmann commented on the pull request:

    What you can actually do to resolve the issue with the `RequestHandler` is to statically
assign them the local JM's address instead of providing a `JobManagerArchiveRetriever`. Since
they are only called when the local JM is the leader, they don't have to look up the current
leader 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: 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

View raw message