[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511329#comment-14511329
]
ASF GitHub Bot commented on FLINK-938:
--------------------------------------
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-95990793
This will work for most use cases where the JobManager is started within
the same cluster as the TaskManagers. It will certainly fail if the JobManager
resides in a different network environment where the hostname cannot be
resolved by the TaskManagers.
I think it's ok to merge if we print a big warning when the job manager
> 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.9
>
>
> 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.3.4#6332)
