You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Liu (Jira)" <ji...@apache.org> on 2022/10/14 09:21:00 UTC

[jira] [Updated] (FLINK-29640) Enhance the function configured by execution.shutdown-on-attached-exit by heartbeat between client and dispatcher

     [ https://issues.apache.org/jira/browse/FLINK-29640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Liu updated FLINK-29640:
------------------------
    Component/s: Client / Job Submission
    Description: 
If the param execution.shutdown-on-attached-exit is set to true, perform a best-effort cluster shutdown when the CLI is terminated abruptly.

But when the client is killed by 'kill -9', the cluster will not shutdown for that the signal can not be sent. We can enhance the behavior by building the heart beat between the client and the job. Once the job can not received any heartbeat from the client, the job cancel itself. 

> Enhance the function configured by execution.shutdown-on-attached-exit by heartbeat between client and dispatcher
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-29640
>                 URL: https://issues.apache.org/jira/browse/FLINK-29640
>             Project: Flink
>          Issue Type: Improvement
>          Components: Client / Job Submission
>            Reporter: Liu
>            Priority: Major
>
> If the param execution.shutdown-on-attached-exit is set to true, perform a best-effort cluster shutdown when the CLI is terminated abruptly.
> But when the client is killed by 'kill -9', the cluster will not shutdown for that the signal can not be sent. We can enhance the behavior by building the heart beat between the client and the job. Once the job can not received any heartbeat from the client, the job cancel itself. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)