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/18 17:11:00 UTC
[jira] [Comment Edited] (FLINK-11629) Stop AkkaRpcActor immediately
after onStop has finished
[ https://issues.apache.org/jira/browse/FLINK-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771146#comment-16771146 ]
Till Rohrmann edited comment on FLINK-11629 at 2/18/19 5:10 PM:
----------------------------------------------------------------
Fixed via c2a443a8c4f2ce8ee3d51e60f667823a9075861a
was (Author: till.rohrmann):
Fixed via 53dbee44538bf0e6fcceaccc77ead945c8a6f161
> Stop AkkaRpcActor immediately after onStop has finished
> -------------------------------------------------------
>
> Key: FLINK-11629
> URL: https://issues.apache.org/jira/browse/FLINK-11629
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.8.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the {{AkkaRpcActor}} sends a {{Kill}} message to itself after the {{onStop}} future has been completed. Since {{Kill}} messages enqueue into the mail box, the stop operation is not immediate. I suggest to rather use {{Context#stop(ActorRef)}} to immediately stop the {{AkkaRcpActor}} upon termination.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)