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/07 21:45:00 UTC
[jira] [Updated] (FLINK-12781) run job REST api doesn't return
complete stack trace for start job failure
[ https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Zhen Wu updated FLINK-12781:
-----------------------------------
Description:
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. But we need the response payload to contain the full stack trace.
was:
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.
```
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The main method caused an error."]}
```
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. But we need the response payload to contain the full stack trace.
> run job REST api doesn't return complete stack trace for start job failure
> --------------------------------------------------------------------------
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: 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. But we need the response payload to contain the full stack trace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)