[ https://issues.apache.org/jira/browse/FLINK-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505309#comment-14505309 ]
Stephan Ewen commented on FLINK-1908: ------------------------------------- I think @DarkKnightCZ is using versiob 0.8.x and [~till.rohrmann] is talking about 0.9 The startup is handled very differently in 0.9 and should actually fix the issue. The selection of the communication interface is in a backoff loop and should happen for many minutes before the TaskManager falls back to heuristics. > 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)