[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626131#comment-14626131
]
ASF GitHub Bot commented on FLINK-938:
--------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-121183870
Yeah, I was also thinking about this.
This will result in a total of 4 combinations:
HA mode | JM address configured | JM address behaviour
------------- | ------------- | -------------
0 | 0 | Use hostname of where the JM is started (new behaviour, this PR)
0 | 1 | Use configured hostname (current behaviour)
1 | 0 | Ignored (current behaviour)
1 | 1 | Ignored (current behaviour)
We would comment out the JM RPC address in the default config and most
cluster setups w/o HA would require one less configuration value.
What do you say? I'm slightly leaning towards adding this, but if your gut
feeling is that this complicates things I'm also happy to close this PR. :)
> 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)
