[
https://issues.apache.org/jira/browse/FLINK-24757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440226#comment-17440226
]
Caizhi Weng commented on FLINK-24757:
-------------------------------------
It seems that we cannot solve it by just setting {{execution.attached}} to
false in SQL client when {{table.dml-sync}} is false and user is submitting an
insert job. This is because some execution environment does not support detach
execution (for example {{LocalExecutor#execute}} just throws an exception).
> Yarn application is not terminated after the job finishes when submitting a
> yarn-per-job insert job with SQL client
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-24757
> URL: https://issues.apache.org/jira/browse/FLINK-24757
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Client
> Affects Versions: 1.14.0
> Reporter: Caizhi Weng
> Priority: Major
> Fix For: 1.15.0, 1.14.1, 1.13.4
>
>
> I've seen this problem for about three times in the user mailing thread
> (previously I suspect that the users are specifying the wrong
> {{{}execution.target{}}}) until I myself also bumped into this problem. I've
> submitted a yarn-per-job batch insert SQL with Flink SQL client and after the
> job finishes Yarn application is not terminated.
> This is because yarn job cluster is using {{MiniDispatcher}} and it will
> directly terminate only in detached execution mode. This execution mode is
> (through some function calls) related to {{DeploymentOptions#ATTACHED}} which
> is true by default if jobs are submitted from SQL client.
> When submitting an insert job, SQL client will not wait for the job to
> finish. Instead it only reports the job id. So I think it is reasonable to
> set detached mode for every insert job.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
