flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1415) Akka cleanups
Date Mon, 26 Jan 2015 15:29:34 GMT

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

ASF GitHub Bot commented on FLINK-1415:

Github user tillrohrmann commented on the pull request:

    I think so too. The changes of the scheduler are only included because otherwise the test
cases wouldn't pass. The scheduler relevant PR is #317.

> Akka cleanups
> -------------
>                 Key: FLINK-1415
>                 URL: https://issues.apache.org/jira/browse/FLINK-1415
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
> Currently, Akka has many different timeout values. From a user perspective, it would
be helpful to deduce all different timeouts from a single timeout value. Additionally, the
user should still be able to define specific values for the different timeouts.
> Akka uses the akka.jobmanager.url config parameter to override the jobmanager address
and the port in case of a local setup. This mechanism is not safe since it is exposed to the
user. Thus, the mechanism should be replaced.
> The notifyExecutionStateChange method allows objects to access the internal state of
the TaskManager actor. This causes NullPointerExceptions when shutting down the actor. This
method should be removed to avoid accessing the internal state of an actor by another object.
> With the latest Akka changes, the TaskManager watches the JobManager in order to detect
when it died or lost the connection to the TaskManager. This behaviour should be tested.

This message was sent by Atlassian JIRA

View raw message