[jira] [Created] (FLINK-24757) Yarn application is not terminated after the job finishes when submitting a yarn-per-job insert job with SQL client

[Caizhi Weng (Jira)]

Caizhi Weng created FLINK-24757:
-----------------------------------

             Summary: 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
             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 suspecting 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 the Yarn application is not terminated.

This is because yarn job cluster is using the {{MiniDispatcher}} and it will 
directly terminated only the detached execution mode. This execution mode is 
(through some function calls) related to {{DeploymentOptions#ATTACHED}} which 
is true by default.

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.3.4#803005)