flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-938) Change start-cluster.sh script so that users don't have to configure the JobManager address
Date Tue, 02 Dec 2014 09:43:12 GMT

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

ASF GitHub Bot commented on FLINK-938:

GitHub user qmlmoon opened a pull request:


    [FLINK-938] Auomatically configure the jobmanager address

    This PR is an alternativ approach to #48 without touching the config file.  Once this
is merged, I'll close #48

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/qmlmoon/incubator-flink hostname2

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #248
commit 6dffd0855e51ddae3a1851cc8752521ac3d41b27
Author: mingliang <qmlmoon@gmail.com>
Date:   2014-12-02T09:37:05Z

    [FLINK-938] Auomatically configure the jobmanager address


> 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

View raw message