jobs but
works in my current environment.
Best regards
Theo
- Ursprüngliche Mail -
Von: "David Morin"
An: "user"
Gesendet: Montag, 23. September 2019 17:21:17
Betreff: Re: How to prevent from launching 2 jobs at the same time
Thanks Till,
Perfect. I gonna use Re
Thanks Till,
Perfect. I gonna use RestClusterClient with listJobs
It should work perfectly for my need
Cheers
David
On 2019/09/23 12:36:46, Till Rohrmann wrote:
> Hi David,
>
> you could use Flink's RestClusterClient and call #listJobs to obtain the
> list of jobs being executed on the cluste
Hi David,
you could use Flink's RestClusterClient and call #listJobs to obtain the
list of jobs being executed on the cluster (note that it will also report
finished jobs). By providing a properly configured Configuration (e.g.
loading flink-conf.yaml via GlobalConfiguration#loadConfiguration) it
Hi,
Thanks for your replies.
Yes, it could be useful to have a way to define jobid. Thus, I would have been
able to define the jbid based on the name for example. At the moment we do not
use the REST API but the cli to submit our jobs on Yarn.
Nevertheless, I can implement a little trick: at sta
The situation is as Dian said. Flink identifies jobs by job id instead of
job name.
However, I think it is still a valid question if it is an alternative Flink
identifies jobs by job name and
leaves the work to distinguish jobs by name to users. The advantages in
this way includes a readable
displ
Hi David,
The jobs are identified by job id, not by job name internally in Flink and so
It will only check if there are two jobs with the same job id.
If you submit the job via CLI[1], I'm afraid there are still no built-in ways
provided as currently the job id is generated randomly when submi
Hi,
What is the best way to prevent from launching 2 jobs with the same name
concurrently ?
Instead of doing a check in the script that starts the Flink job, I would
prefer to stop a job if another one with the same name is in progress
(Exception or something like that).
David
