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

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/11/03 07:53:00 UTC

[jira] [Commented] (FLINK-28598) ClusterEntryPoint can't get the real exit reason when shutting down

    [ https://issues.apache.org/jira/browse/FLINK-28598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628167#comment-17628167 ] 

Yun Gao commented on FLINK-28598:
---------------------------------

[~zlzhang0122] May I have a double confirmation of the issue that which deployment mode you are using? Since I'm not quite sure which part the user code would be executed during starting. 

> ClusterEntryPoint can't get the real exit reason when shutting down
> -------------------------------------------------------------------
>
>                 Key: FLINK-28598
>                 URL: https://issues.apache.org/jira/browse/FLINK-28598
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN, Runtime / Task
>    Affects Versions: 1.14.2, 1.15.1
>            Reporter: zlzhang0122
>            Priority: Major
>
> When the cluster is starting and some error occurs, the ClusterEntryPoint will shutDown the cluster asynchronous, but if it can't get a Throwable, the shutDown reason will be null, but actually if it's a user code problem and this may happen. 
> I think we can get the real exit reason caused by user code and pass it to the diagnostics parameter, this may help users a lot.



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