[
https://issues.apache.org/jira/browse/FLINK-16637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061328#comment-17061328
]
Zili Chen commented on FLINK-16637:
-----------------------------------
[~chaiyq] Thanks for your reminding. I've linked these two issues.
It seems there are two problems here
1. After FLINK-15116 we synchronously shutdown the cluster after job cancelled
so that it can never serve the result.
2. Even without FLINK-15116 there is a risk we don't clear outstanding response
futures before the server down.
Before we agree on these two reason I will keep both of issues open, and I will
try to look into the problem the next day. But tbh, I don't have a plan so far.
> Flink per job mode terminates before serving job cancellation result
> --------------------------------------------------------------------
>
> Key: FLINK-16637
> URL: https://issues.apache.org/jira/browse/FLINK-16637
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.10.0
> Reporter: Zili Chen
> Priority: Major
> Fix For: 1.10.1, 1.11.0
>
> Attachments: yarn.log
>
>
> The {{MiniDispatcher}} no longer waits until the REST handler has served the
> cancellation result before shutting down. This behaviour seems to be
> introduced with FLINK-15116.
> See also
> [https://lists.apache.org/x/thread.html/rcadbd6ceede422bac8d4483fd0cdae58659fbff78533a399eb136743@%3Cdev.flink.apache.org%3E]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
