flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-1580) Cleanup TaskManager initialization logic
Date Mon, 06 Apr 2015 15:52:12 GMT

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

Stephan Ewen resolved FLINK-1580.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9
         Assignee: Stephan Ewen

Fixed via e74521c1fe5f5842185be5c454d27adc3bd254d5

> Cleanup TaskManager initialization logic
> ----------------------------------------
>
>                 Key: FLINK-1580
>                 URL: https://issues.apache.org/jira/browse/FLINK-1580
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
>            Assignee: Stephan Ewen
>             Fix For: 0.9
>
>
> Currently, the TaskManager initializes many heavy load objects upon registration at the
JobManager. If an exception occurs during the initialization it takes quite long until the
{{JobManager}} detects the {{TaskManager}} failure.
> Therefore, it would be better if we could rearrange the initialization logic so that
the {{TaskManager}} only registers at the {{JobManager}} if the all objects could be initialized
successfully. Moreover, it would be worthwhile to move some of the initialization work out
of the {{TaskManager}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message