[jira] [Commented] (FLINK-938) Change start-cluster.sh script so that users don't have to configure the JobManager address

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220785#comment-14220785 ] 

ASF GitHub Bot commented on FLINK-938:
--------------------------------------

Github user StephanEwen commented on the pull request:

    https://github.com/apache/incubator-flink/pull/48#issuecomment-63957478
  
    I am skeptical whether it is a good idea to modify the config file at all. I bet that many people make the implicit assumption that this file is constant. And modifying it when the host is "localhost" is hidden  constraint that makes it tricky to understand why the script sometimes configures things for you and sometimes not.
    
    I vote for an approach to add this as a command line parameter to the ssh-transmitted call to start the taskmanager. The command line parser should check for that argument similarly as it checks for the config directory.


> 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.8-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.3.4#6332)