replication job failed,but do not re-scheduled

[dantianji]

when the replication job failed,it doesn't be re-scheduled a few minutes later.
2019-05-08T15:01:22Z [INFO] initialization completed: repository: 20000000240/dq-yhqmanage, tags: [20190508225913177407807], source registry: URL-https://172.78.225.35 insecure-true, destination registry: URL-https://172.78.225.30 insecure-true
2019-05-08T15:01:22Z [ERROR] [job_logger.go:81]: an error occurred while creating project 20000000240 on destination registry: Post https://172.78.225.30/api/projects/: dial tcp 10.70.62.230:443: getsockopt: connection refused

[heww]

@dantianji Can you confirm that the cron string is correct?

I tested that replication job will scheduled even one job failed.

Can you provide more detail info?

[541013515]

I met same errors， like this：

did two jobs trigger image replication to same destination at same time causing this problem？

[steven-zou]

@dantianji

Is it a periodic job with a pre-defined schedule or is just a once-running job? Failed jobs will be retried if it does not reach the top ceil. Moreover, which Harbor version are you using? If it is 1.8.x, job retrying may have a bug which is referred in the issue #8745.

[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.