[
https://issues.apache.org/jira/browse/FLINK-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501279#comment-14501279
]
ASF GitHub Bot commented on FLINK-1908:
---------------------------------------
GitHub user DarkKnightCZ opened a pull request:
https://github.com/apache/flink/pull/609
[FLINK-1908] JobManager startup delay isn't considered when using
start-cluster.sh script
Creates dependency on netcat package (nc)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DarkKnightCZ/flink FLINK-1908
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/609.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #609
----
commit a48eea0108e6bd19a826182e5f692f9561ec887c
Author: Lukáš Raška <lu...@raska.me>
Date: 2015-04-18T11:26:54Z
[FLINK-1908] Use netcat to check if JobManager is accessible via RPC, 30
seconds timeout
----
> JobManager startup delay isn't considered when using start-cluster.sh script
> ----------------------------------------------------------------------------
>
> Key: FLINK-1908
> URL: https://issues.apache.org/jira/browse/FLINK-1908
> Project: Flink
> Issue Type: Bug
> Components: Distributed Runtime
> Affects Versions: 0.9, 0.8.1
> Environment: Linux
> Reporter: Lukas Raska
> Priority: Minor
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> When starting Flink cluster via start-cluster.sh script, JobManager startup
> can be delayed (as it's started asynchronously), which can result in failed
> startup of several task managers.
> Solution is to wait certain amount of time and periodically check if RPC port
> is accessible, then proceed with starting task managers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
