[
https://issues.apache.org/jira/browse/FLINK-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502736#comment-14502736
]
ASF GitHub Bot commented on FLINK-1908:
---------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/609#issuecomment-94444121
The TaskManager's maximum registration duration is configured by the config
value ```taskmanager.maxRegistrationDuration```. The default value is set to
infinity for a dedicated Flink cluster.
Therefore, I'm wondering what exactly the problem with the startup delay
is? @DarkKnightCZ maybe you can elaborate a little bit more on the problem you
had.
> 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)
