Chlins Zhang

@lengrongfu Great thanks for your contribution to harbor, but as I replied in the issue: https://github.com/goharbor/harbor/issues/17356#issuecomment-1214819739, we should close this pr now and open a discussion for this.

@withlin Hi, could you check the job status from database? (ref: `select status from execution group by status`)

Could you query those running executions? `select * from execution where status='Running'`

So do you still have the running retention jobs in your harbor? It seems the execution time is too long such as `id= 5136658 `, the possibility is either it...

From the error log, maybe your jobs were in the unrecoverable status, you could refer to https://github.com/goharbor/harbor/wiki/Harbor-FAQs#job-service and then restart harbor service, for tag retention job harbor will do enhancement...

Could you share the current size of your data(such as repo and artifacts numbers) and the frequency of previous retention executions?

In my opinion, retention job can help to reduce the artifacts numbers in the harbor which can help to maintain, but this feature should work with GC because retention only...

> > In my opinion, retention job can help to reduce the artifacts numbers in the harbor which can help to maintain, but this feature should work with GC because...

Could you provide your nginx configuration? It seems your haproxy trim auth header when proxy requests.

You could refer to https://github.com/goharbor/harbor/issues/3114.