[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626177#comment-14626177
]
ASF GitHub Bot commented on FLINK-938:
--------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-121195803
I've tested this with default EC2 and GCE instances, which by default
return the cloud internal hostname. I would say that this is a reasonable
configuration. If it is not configured this way, the address needs to be
configured (which is the current behavior). With a good startup/error message
this should be fine.
Still, I start to feel like we are discussing this issue for too long w/o
anybody asking for it. Since we have to rebase this on the recent big changes
anyways, let's close this PR and reconsider it the issue if someone
complains/asks for it. Agree?
> 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)
