/usr/bin/DO_NOT_USE_GC process continuously running

[flyingfishflash]

At some point around a month ago, I noticed my nas cpu usage went up, so I took a look and found that multiple instances of
what looks like the garbage collection process are running constantly.

This happens no matter, some time after I start up the system via docker compose.

I am using harbor 2.14 and put the logs in debug mode and watch for those processes to suddenly start up via htop. I am not actually sure what triggers them.

I see no log message indicating what may be starting it. If i restart everything via docker compose and run a manual gc it works fine, I see the process in htop, but it finishes very quickly and cpu usage returns to normal.

SOMETHING is trigger this, and at the same time i see numerous entries like this with a short pause, then resuming endlessly until i restart harbor.

Oct 12 16:35:32 nas docker[3068698]: registry           | time="2025-10-12T20:35:32.286392322Z" level=debug msg="s3aws.ListObjectsV2Pages(data/docker/registry/v2/repositories/docker.io/postgres/_uploads/4b327acc-1c60-492e-b0c0-3972503aa0b8/)" go.version=go1.24.6 instance.id=8ec11b9f-174f-4558-a6f7-809fae5f6d79 service=registry trace.duration=3.446017ms trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/s3-aws/s3.go" trace.func="github.com/docker/distribution/registry/storage/driver/s3-aws.(*driver).doWalk" trace.id=33d3c125-b528-4346-bd67-6530fdf20fd4 trace.line=980 trace.parent.id=a0a37bfe-0ea8-4584-8cdf-335effeaf327 version=v2.8.3-23-g0c62ec3e
Oct 12 16:35:32 nas docker[3068698]: registry           | time="2025-10-12T20:35:32.289911978Z" level=debug msg="s3aws.ListObjectsV2Pages(data/docker/registry/v2/repositories/docker.io/postgres/_uploads/4b537766-b35e-42a0-a0ef-40bcf7bb358b/hashstates/sha256/)" go.version=go1.24.6 instance.id=8ec11b9f-174f-4558-a6f7-809fae5f6d79 service=registry trace.duration=1.133947ms trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/s3-aws/s3.go" trace.func="github.com/docker/distribution/registry/storage/driver/s3-aws.(*driver).doWalk" trace.id=542e6ae6-4456-42b5-bc12-c23f4bc20fdd trace.line=980 trace.parent.id=5f1422c5-adec-40b5-86cd-d328eacb5134 version=v2.8.3-23-g0c62ec3e

it's referencing a repo that is manage by a replication job. I tried deleting the repo but still this it eventually triggered.

I'm using seaweedfs for s3 storage. I guess it could be somehow caused by that, but I see no errors there.

Anyone have any idea what may be causing this?

Hoping to avoid having to go through the pain of recreating my installation.

Disabling the Garbage Collection job does not prevent this from occurring.

Not sure why disabling the replication that creates docker.io/postgres and deleting the project doesn't stop this activity?

Thanks

[stonezdj]

It is a backend go routine to remove the temporary files under _uploads directory, it is OK to let it run.

[flyingfishflash]

yes I can confirm that changing the registry configuration to no purge uploads prevented this activity from occurring