ursday, January 21, 2021 10:00 AM
To: Hailu, Andreas [Engineering]
mailto:andreas.ha...@ny.email.gs.com>>
Cc: user@flink.apache.org<mailto:user@flink.apache.org>
Subject: Re: org.apache.flink.runtime.client.JobSubmissionException: Job has
already been submitted
Thanks a lot for y
*From:* Robert Metzger
> *Sent:* Thursday, January 21, 2021 10:00 AM
> *To:* Hailu, Andreas [Engineering]
> *Cc:* user@flink.apache.org
> *Subject:* Re: org.apache.flink.runtime.client.JobSubmissionException:
> Job has already been submitted
>
>
>
> Thanks a lot fo
this application. Is it possible that it’s busy processing other
jobs?
// ah
From: Robert Metzger
Sent: Thursday, January 21, 2021 10:00 AM
To: Hailu, Andreas [Engineering]
Cc: user@flink.apache.org
Subject: Re: org.apache.flink.runtime.client.JobSubmissionException: Job has
already been
(CompletableFuture.java:561)
>
>at
> java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:929)
>
>at
> java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
>
>... 3 more
>
> Ca
Hello,
We're running 1.9.2 on YARN, and are seeing some interesting behavior when
submitting jobs in a multi-threaded fashion to an application's Flink cluster.
The error we see reported in the client application logs is the following:
org.apache.flink.client.program.ProgramInvocationException:
