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

Posted to issues@flink.apache.org by "zlzhang0122 (Jira)" <ji...@apache.org> on 2022/07/19 02:43:00 UTC

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

zlzhang0122 created FLINK-28598:
-----------------------------------

             Summary: 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.15.1, 1.14.2
            Reporter: zlzhang0122


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)