[
https://issues.apache.org/jira/browse/FLINK-16703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-16703.
-----------------------------------
Resolution: Fixed
Fixed via
1.11.0: 1e0db6425f18b8d69b69176b9cb75e8b000bf768
1.10.1: 8773895b6b7cf75ee642ebd1496c0566a0ddaa40
1.9.3: b71c4002d3942f48807d2b5c0ac64ee3e55b2f59
> AkkaRpcActor state machine does not record transition to terminating state.
> ---------------------------------------------------------------------------
>
> Key: FLINK-16703
> URL: https://issues.apache.org/jira/browse/FLINK-16703
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.8.0, 1.9.0, 1.10.0, 1.11.0, 2.0.0
> Reporter: Dmitri Chmelev
> Assignee: Till Rohrmann
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.9.3, 1.10.1, 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As part of FLINK-11551, the state machine of AkkaRpcActor has been updated to
> include 'terminating' and 'terminated' states. However, when actor
> termination request is handled, the resulting 'terminating' state is not
> updated by the FSM.
> [https://github.com/apache/flink/blame/master/flink-runtime/src/main/java/org/apache/flink/runtime/rpc/akka/AkkaRpcActor.java#L175]
> As a side-effect, {{isRunning()}} predicate can return that the actor is
> still running after terminate was initiated and to still handle messages.
> I believe the fix is trivial and the private field {{state}} should be
> updated with the return value of the call to {{state.terminate()}}.
> Feel free to adjust the priority accordingly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
