Some Harbor Jobs should not run in parallel as it causes DB deadlocks

[Vad1mo]

Some jobs that should not run in parallel; however, some do run in parallel, even if it is set in the code otherwise.

Running jobs in parallel, here the GC job causes the DB to Lock, and put the system in a not usable state.

Steps to reproduce the problem:

• Run jobs in parallel, specifically the GC job

Versions:
Please specify the versions of the following systems.

• harbor version: >=2.11

Additional context:

[wy65701436]

do you mean that you run the GC in parallel which results in the deadlock in the DB side?

The GC is designed as a unique job and should not be able to run in parallel. But, if you were able to do so, please provide the environment details so I can investigate further.

[Vad1mo]

The GC is designed as a unique job and should not be able to run in parallel. But, if you were able to do so, please provide the environment details so I can investigate further.

It is quite simple, I was able to replicated it in the demo environment:

https://demo.goharbor.io/harbor/clearing-job/gc