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] [Commented] (FLINK-1580) Cleanup TaskManager initialization logic
Date Tue, 24 Feb 2015 21:16:04 GMT

    [ https://issues.apache.org/jira/browse/FLINK-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335468#comment-14335468

Stephan Ewen commented on FLINK-1580:

Partially solved in ed8b26bf2e8dd7c187c24ad0d8ff3e67f6a7478c

> Cleanup TaskManager initialization logic
> ----------------------------------------
>                 Key: FLINK-1580
>                 URL: https://issues.apache.org/jira/browse/FLINK-1580
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
> 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

View raw message