[
https://issues.apache.org/jira/browse/FLINK-25715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509665#comment-17509665
]
Robert Metzger commented on FLINK-25715:
----------------------------------------
Thanks a lot for adding this feature!
One thing that is not yet covered are issues loading the job class from the
classloader. As you can see here, such issues will kill the process:
https://github.com/apache/flink/blob/master/flink-container/src/main/java/org/apache/flink/container/entrypoint/StandaloneApplicationClusterEntryPoint.java#L65-L77
Since users often misconfigure the main class name, it would be useful to also
report these errors. I don't see a fundamental reason why we can't lazily
initialize the PackagedProgram in the
{{ApplicationDispatcherBootstrap.runApplicationEntryPoint}} or somewhere in
this area. If you agree, I'll create a ticket to track this feature request.
> Application Mode: Add option to submit a failed job on application error
> ------------------------------------------------------------------------
>
> Key: FLINK-25715
> URL: https://issues.apache.org/jira/browse/FLINK-25715
> Project: Flink
> Issue Type: New Feature
> Components: Client / Job Submission, Runtime / Coordination
> Reporter: David Morávek
> Assignee: David Morávek
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> Currently in application mode, any exception happens in the application
> driver (before submitting an actual job) leads to a fail-over. These errors
> are usually not retryable and we don't have a good way of reporting them to
> the user.
> We'll introduce a new config option
> `execution.submit-failed-job-on-application-error` that submits a failed job
> with the `$internal.pipeline.job-id` instead.
> This is intended to be used in combination with
> `execution.shutdown-on-application-finish = false` to allow user to retrieve
> the information about the failed submission.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
