[
https://issues.apache.org/jira/browse/FLINK-9045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409267#comment-16409267
]
Stephan Ewen commented on FLINK-9045:
-------------------------------------
All right, this may be actually just a change in the way its described in the
logs then.
Not sure if users (including me ;-)) make the connection between dispatcher and
web UI.
In earlier versions, we explicitly logged that the web UI started (and I think
we tried to start it at the default port 8081).
Can we
- at least log that the web ui is started at port xyz when we have this flag?
- make sure that this behavior stays, when in the future the local
environment possibly does not use a dispatcher any more
- possibly try and start the web server at the default port, so users don't
have to scan the logs to find the random port?
Orthogonal: Why does this even start a dispatcher? The local environment should
be able to directly submit to the mini cluster, no dispatcher needed.
> LocalEnvironment with web UI does not work with flip-6
> ------------------------------------------------------
>
> Key: FLINK-9045
> URL: https://issues.apache.org/jira/browse/FLINK-9045
> Project: Flink
> Issue Type: Bug
> Components: Webfrontend
> Reporter: Stephan Ewen
> Assignee: Chesnay Schepler
> Priority: Blocker
> Fix For: 1.5.0
>
>
> The following code is supposed to start a web UI when executing in-IDE. Does
> not work with flip-6, as far as I can see.
> {code}
> final ExecutionEnvironment env =
> ExecutionEnvironment.createLocalEnvironmentWithWebUI(new Configuration());
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
