You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Steven Zhen Wu (JIRA)" <ji...@apache.org> on 2019/06/08 20:55:00 UTC
[jira] [Assigned] (FLINK-12781) REST handler should return full
stack trace instead of just error msg
[ https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Zhen Wu reassigned FLINK-12781:
--------------------------------------
Assignee: Steven Zhen Wu
> REST handler should return full stack trace instead of just error msg
> ---------------------------------------------------------------------
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: Steven Zhen Wu
> Assignee: Steven Zhen Wu
> Priority: Major
>
> We use REST api to start a job in Flink cluster.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
> When there is exception during job construction, the response payload doesn't contain the full stack trace.
> {code}
> {"errors":["org.apache.flink.client.program.ProgramInvocationException: The main method caused an error."]}
> {code}
> This problem becomes more serious after FLINK-11134 got released in 1.7.2, because stack trace is completely lost now. FLINK-11134 is doing the right thing. We just need the response payload to contain the full stack trace, which seems to have been an issue/fix since 1.5. we know 1.4 doesn't have this issue and correctly return full stack trace
> on the jobmanager log, we only get
> {code}
> 2019-06-07 17:42:40,136 ERROR org.apache.flink.runtime.webmonitor.handlers.JarRunHandler - Exception occurred in REST handler: org.apache.flink.client.program.ProgramInvocationException: The main method caused an error.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)