You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/02/26 16:58:00 UTC

[jira] [Closed] (FLINK-5176) Properly wait for component shutdown in Runner components

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

Till Rohrmann closed FLINK-5176.
--------------------------------
    Resolution: Done

Done with the Flip-6 refactorings.

> Properly wait for component shutdown in Runner components
> ---------------------------------------------------------
>
>                 Key: FLINK-5176
>                 URL: https://issues.apache.org/jira/browse/FLINK-5176
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination
>            Reporter: Till Rohrmann
>            Assignee: Shuyi Chen
>            Priority: Minor
>              Labels: flip-6
>
> Currently, the different runners for the Flip-6 components {{JobMaster}}, {{ResourceManager}} and {{TaskExecutor}} don't wait until the component has been shut down in their own {{shutDown}} method. The problem is that the {{AkkaRpcService}} implements the {{RpcService#shutDown}} method via a {{PoisonPill}} which is not executed synchronously. Instead we should obtain the {{RpcEndpoint#getTerminationFutures}} and wait on the returned future (with a given timeout).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)