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-2769) Web dashboard port not configurable on client side
Date Thu, 10 Dec 2015 12:21:11 GMT

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

ASF GitHub Bot commented on FLINK-2769:
---------------------------------------

Github user uce commented on the pull request:

    https://github.com/apache/flink/pull/1449#issuecomment-163594437
  
    Thanks! It was 2769 and not 2796. Updated the PR.


> Web dashboard port not configurable on client side
> --------------------------------------------------
>
>                 Key: FLINK-2769
>                 URL: https://issues.apache.org/jira/browse/FLINK-2769
>             Project: Flink
>          Issue Type: Bug
>          Components: Webfrontend
>    Affects Versions: 0.10.0
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>            Priority: Critical
>             Fix For: 0.10.0
>
>
> The new web dashboard port configuration only affects the server side, but not the client
side.
> To reproduce set in {{flink-conf.yaml}}:
> {code}
> jobmanager.web.port: 9091
> jobmanager.new-web-frontend: true
> {code}
> Run
> {code}
> $ bin/start-cluster.sh
> {code}
> You can browse to {{http://localhost:9091}}, but you won't see any data from the job
manager. Requests to http://localhost:9091/overview etc. work as expected, but the client
side JavaScript is running requests against {{http://localhost:8081}}.
> The problem is that {{flink-runtime-web/web-dashboard/app/scripts/index.coffee}} hard
codes:
> {code}
> .value 'flinkConfig', {
>   jobServer: 'http://localhost:8081'
> }
> {code} which is picked up by all generated scripts.
> This needs to be configurable for both standalone mode but especially for recovery mode.
This was a major pain point for me today, because I was working on the dashboard and thought
that my changes were wrong.
> In general, we need to add more tests to the new dashboard, which should soon replace
the old one imo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message