[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098432#comment-14098432
]
ASF GitHub Bot commented on FLINK-938:
--------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/incubator-flink/pull/48#issuecomment-52294123
Then I think we need a bit of a different approach.
Can we remove the jobmanager rpc address from the config file, and have the
script check whether there is an entry for the jobmanager address. If not, it
uses the local hostname.
I would actually prefer to have something like a `.jobmanager` file in
yarn, rather than rewriting the config. Seems much cleaner.
> Change start-cluster.sh script so that users don't have to configure the
> JobManager address
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-938
> URL: https://issues.apache.org/jira/browse/FLINK-938
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Reporter: Robert Metzger
> Assignee: Mingliang Qi
> Priority: Minor
> Fix For: 0.6-incubating
>
>
> To improve the user experience, Flink should not require users to configure
> the JobManager's address on a cluster.
> In combination with FLINK-934, this would allow running Flink with decent
> performance on a cluster without setting a single configuration value.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
