You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2018/07/19 15:46:00 UTC

[jira] [Updated] (FLINK-9732) Report more detailed error message on JobSubmissionFailure

     [ https://issues.apache.org/jira/browse/FLINK-9732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

vinoyang updated FLINK-9732:
----------------------------
    Summary: Report more detailed error message on JobSubmissionFailure  (was: Report more detailed error message on SobSubmissionFailure)

> Report more detailed error message on JobSubmissionFailure
> ----------------------------------------------------------
>
>                 Key: FLINK-9732
>                 URL: https://issues.apache.org/jira/browse/FLINK-9732
>             Project: Flink
>          Issue Type: Improvement
>          Components: REST
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Chesnay Schepler
>            Assignee: vinoyang
>            Priority: Major
>
> Currently, if the job submission through the {{JobSubmitHandler}} fails the error message returned tot he client only says "Job submission failed.".
> As outlined in the discussion in this [PR|https://github.com/apache/flink/pull/6222] we should try to include more information about the actual failure cause.
> The proposed solution is to encode the cause for the failure in the {{Acknowledge}} that is returned by {{DispatcherGateway#submitJob}}.
> {code}
> public class AckOrException {
> 	// holds exception, could also be a series of nullable fields
> 	private final SuperEither<ExceptionA, ExceptionB, ExceptionC> exception; 
> 	...
> 	public void throwIfError() throws ExceptionA, ExceptionB, ExceptionC;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)