after stop replication job, the task is actually still running for a while

[bitsf]

Currently when user click stop job, it just set a stop marker in database, and jobservice will break job at some check point.
But if user is copying a big blob, or use replication bandwidth limit (in v2.4), that may need quite a long time before the jobs really exit. Because there isn't any checkpoint inside PushBlob()

harbor/src/controller/replication/transfer/image/transfer.go

Line 331 in 93e6441

if err = t.dst.PushBlob(dstRepo, digest, size, data); err != nil {

The side effect is other executions/tasks may not be scheduled because usually only 10 concurrent workers, and you will see job pending status and log NOT_FOUND problem.
{"errors":[{"code":"NOT_FOUND","message":"{\"code\":10010,\"message\":\"object is not found\",\"details\":\"1537612e372ab09cb9bba00f\"}"}]}

user has to restart jobservice container if he want to force stop the network transfer.

[zyyw]

wait for feedback from users

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.