We are running harbor registry 2.12 using Harbor Helm config in two AWS TKG (actually Palette) environments of about the same size (Env 1=100tb, Env 2=136tb and growing). We use an external AWS RDS postgresql database with S3 storage for manifests, layers, and blobs. Env 1 runs Harbor garbage collection daily and successfully. When executed, the GC TASK table row goes immediately to 'Running' status as expected.

Env 2 is growing because garbage collection, when executed, goes immediately into 'Pending' status (per Postgresql TASK table). The Env 2 ARTIFACT_TRASH table now contains 107,000 entries vs Env 1's 5,000+. No ARTIFACT_TRASH records are being deleted. Env 2 Garbage collection was running fine for about a year until 2025-03-07. Its TASK suddenly began going into Pending status right from the beginning of the GC execution. We are not aware of any events on 03-06 or 03-07 that might have impacted GC.

We figure Env 2 hit some condition (perhaps from distribution) and returned a status code that Harbor interprets as 'Pending'. Conditions might include data sync situations caused by a prior network, Palette, Harbor, security or infrastructure failure. The Harbor application in Env 2 continues to operate as expected for our 6,000 users. GC is the only concern.

Can you offer one or more conditions in the Distribution or Harbor app that would cause Harbor to set the GC task status to Pending? What other info can we provide

FROM POSTGRESQL EXECUTION TABLE

FROM POSTGRESQL TASK TABLE