flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Raska (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-1908) JobManager startup delay isn't considered when using start-cluster.sh script
Date Wed, 29 Apr 2015 17:40:06 GMT

     [ https://issues.apache.org/jira/browse/FLINK-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lukas Raska resolved FLINK-1908.
--------------------------------
    Resolution: Won't Fix

As TMs work differently in 0.9 and this issue doesn't occur there, it probably won't be fixed
in 0.8.1

> 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.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)

Mime
View raw message