[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044466#comment-14044466
]
ASF GitHub Bot commented on FLINK-938:
--------------------------------------
Github user rmetzger commented on the pull request:
https://github.com/apache/incubator-flink/pull/48#issuecomment-47200290
I guess the rewrite of the yaml file works well with this pull request. But
I think this approach is not always working.
This approach assumes that the configuration file is shared among all
cluster nodes (for example via NFS).
I would implement this by passing (via the cli invocation) the Jobmanager's
hostname (or ip address) to the TaskManagers when starting them and leave the
yaml file untouched.
> 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
> Reporter: Robert Metzger
> Assignee: Mingliang Qi
> 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)
