You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/02/13 13:16:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17687933#comment-17687933 ] 

Matthias Pohl commented on FLINK-29640:
---------------------------------------

[~Jiangang] does it make sense to add release notes to this Jira issue? AFAIS, we're introducing new config parameters here which might be worth mentioning in the 1.17 release notes.

> 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
>            Assignee: Liu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.17.0
>
>
> 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)