Hi Robert,
Yeah, I know. For the moment, I warned my colleagues not to call System.exit()
:-) But it needs to be implemented for the sake of Flink usability as you
described in the issue.
Thanks a lot for taking care of this issue.
Best,
Dongwon
> 2019. 12. 9. 오후 9:55, Robert Metzger 작성:
>
Hey Dongwon,
I filed a ticket: https://issues.apache.org/jira/browse/FLINK-15156
This does not mean it will be implemented anytime soon :)
On Mon, Dec 9, 2019 at 2:25 AM Dongwon Kim wrote:
> Hi Robert and Roman,
> Yeah, letting users know System.exit() is called would be much more
> appropriate
Hi Robert and Roman,
Yeah, letting users know System.exit() is called would be much more
appropriate than just intercepting and ignoring.
Best,
Dongwon
On Sat, Dec 7, 2019 at 11:29 PM Robert Metzger wrote:
> I guess we could manage the security only when calling the user's main()
> method.
>
>
I guess we could manage the security only when calling the user's main()
method.
This problem actually exists for all usercode in Flink: You can also kill
TaskManagers like this.
If we are going to add something like this to Flink, I would only log that
System.exit() has been called by the user
Hi Dongwon,
This should work but it could also interfere with Flink itself exiting in
case of a fatal error.
Regards,
Roman
On Fri, Dec 6, 2019 at 2:54 AM Dongwon Kim wrote:
> FYI, we've launched a session cluster where multiple jobs are managed by a
> job manager. If that happens, all the
FYI, we've launched a session cluster where multiple jobs are managed by a
job manager. If that happens, all the other jobs also fail because the job
manager is shut down and all the task managers get into chaos (failing to
connect to the job manager).
I just searched a way to prevent
Hi Robert and Roman,
Thank you for taking a look at this.
what is your main() method / client doing when it's receiving wrong program
> parameters? Does it call System.exit(), or something like that?
>
I just found that our HTTP client is programmed to call System.exit(1). I
should guide not to
Hi Dongwon,
what is your main() method / client doing when it's receiving wrong program
parameters? Does it call System.exit(), or something like that?
By the way, the http address from the error message is publicly available.
Not sure if this is internal data or not.
On Thu, Dec 5, 2019 at
Hi Dongwon,
I wasn't able to reproduce your problem with Flink JobManager 1.9.1 with
various kinds of errors in the job.
I suggest you try it on a fresh Flink installation without any other jobs
submitted.
Regards,
Roman
On Thu, Dec 5, 2019 at 3:48 PM Dongwon Kim wrote:
> Hi Roman,
>
> We're
Hi Roman,
We're using the latest version 1.9.1 and those two lines are all I've seen
after executing the job on the web ui.
Best,
Dongwon
On Thu, Dec 5, 2019 at 11:36 PM r_khachatryan
wrote:
> Hi Dongwon,
>
> Could you please provide Flink version you are running and the job manager
> logs?
Hi Dongwon,
Could you please provide Flink version you are running and the job manager
logs?
Regards,
Roman
eastcirclek wrote
> Hi,
>
> I tried to run a program by uploading a jar on Flink UI. When I
> intentionally enter a wrong parameter to my program, JobManager dies.
> Below
> is all log
Hi,
I tried to run a program by uploading a jar on Flink UI. When I
intentionally enter a wrong parameter to my program, JobManager dies. Below
is all log messages I can get from JobManager; JobManager dies as soon as
spitting the second line:
2019-12-05 04:47:58,623 WARN
>
12 matches
Mail list logo
