[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509047#comment-14509047
]
ASF GitHub Bot commented on FLINK-938:
--------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-95586174
I've rebased this on the current master, added log messages when falling
back to the default address (which I've renamed as Till suggested), and tested
it.
There is one remaining issue though: When starting the task manager, you
use `hostname` as the default JM address. As @StephanEwen pointed out in
another thread [1], this will only work for certain setups. Then the question
is whether we really improve deployment with this or not. @rmetzger, you
reported the original issue. Do you (and others of course) have an idea about
this?
[1] https://github.com/apache/flink/pull/581#issuecomment-94911176
PS: The rebased branch is here, if you have time to pick it up from there:
https://github.com/uce/incubator-flink/tree/jmaddress
> 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)
