liupc opened a new pull request #9923: [FLINK-14429][YARN]Fix wrong app final status when running batch job on yarn with non detached mode flink14429 URL: https://github.com/apache/flink/pull/9923 ## What is the purpose of the change Currently, The app final status is not correct when an application failed when running batch job on yarn with non-detached mode, It reported SUCCEEDED but FAILED is what we expected.(e.g. failures caused by taskManager oom, client exits and etc.) This PR is trying to make the final status correct. ## Brief change log - Update Shutdown rpc messages to to bring appStatus and diagnostics messages. - Calling code paths. - Shutdown future related ## Verifying this change This change is verified with an terasort app, we tested it on yarn with non-detached mode. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
