Github user zhijiangW commented on the issue:
https://github.com/apache/flink/pull/3360
@StephanEwen , if the exception is bubbled out, and cause TaskExecutor to
exit as a result, I think the JobMaster can be assumed in a sane state in final
based on detection of TaskExecutor failure.
The current solution just refers to OOM error, maybe it can extend to any
exceptions, because it is difficult to confirm the consistency of the internal
state and the conservative approach is to let it terminate as @tillrohrmann
said.
If I understand correctly from @tillrohrmann 's suggestions, the
**RpcEndpoint.runAsync** method would modify to return a **Future** that is
similar with **RpcEndpoint.callAsync**, but still a **Tell** action in akka.
And this **Future** should be set as a field in **RunAsync** in order to get it
when handle in **AkkaRpcActor**. The **Future** can help to determine whether
the message is executed successfully or lost to enhance the **Tell** mechanism.
If the **Future** with **Tell** action is better than current ** RpcEndpoint
.callAsync** which refers to **Ask** action, I will try to do for that. Or
another option is tolerating the lost message in current
**RpcEndpoint.runAsync**, and it should be used in such scenarios for
efficiency and not safe. For the important interaction, it should resort to
**RpcEndpoint.callAsync**. What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
