Hi Wouter,
I’ve upgraded Flink to 1.8, but now I only see Internal server error on the
dashboard when a job deployment fails.
[cid:image001.png@01D50F44.B76CA0C0]
But in the logs I see the correct exception -
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at
functions.PersistPIDMessagesToCassandra.main(PersistPIDMessagesToCassandra.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:529)
... 9 more
Is there any way to show these errors on the dashboard? Because many
application teams deploy jobs through the dashboard and don’t have ready access
to the logs.
Thanks,
Harshith
From: Wouter Zorgdrager <w.d.zorgdra...@tudelft.nl>
Date: Thursday, 16 May 2019 at 7:56 PM
To: Harshith Kumar Bolar <hk...@arity.com>
Cc: user <user@flink.apache.org>
Subject: [External] Re: Flink not giving full reason as to why job submission
failed
Hi Harshith,
This was indeed an issue in 1.7.2, but fixed in 1.8.0. See the corresponding
Jira issue [1].
Cheers,
Wouter
[1]:
https://issues.apache.org/jira/browse/FLINK-11902<https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_FLINK-2D11902&d=DwMFaQ&c=gtIjdLs6LnStUpy9cTOW9w&r=61bFb6zUNKZxlAQDRo_jKA&m=mnxsj0sRDEDo66PWXKz0vcnqyR6N6FFcRT1a8fQQ_tQ&s=ExTlIDAtlDhFXbfvmWEX7sSHnlu6sLz3SdyB9-1Hv60&e=>
Op do 16 mei 2019 om 16:05 schreef Kumar Bolar, Harshith
<hk...@arity.com<mailto:hk...@arity.com>>:
Hi all,
After upgrading Flink to 1.7.2, when I try to submit a job from the dashboard
and there's some issue with the job, the job submission fails with the
following error.
Exception occurred in REST handler:
org.apache.flink.client.program.ProgramInvocationException: The main method
caused an error.
There's no other reason given as to why the job failed to submit. This was not
the case in 1.4.2. Is there a way to see the full reason why the job failed to
deploy? I see the same error in the logs too with no additional information.
Thanks,
Harshith
