First, I noticed we are running the full sync twice right now, at the
same time:
[root@mm-backend01 cron.d][PROD]# cat /etc/cron.d/s3.sh
#Ansible: s3sync
0 0,11 * * * s3-mirror /usr/local/bin/lock-wrapper s3sync /usr/local/bin/s3.sh 2>&1
| /usr/local/bin/nag-once s3.sh 1d 2>
&1
#Ansible: s3sync-main
0 0 * * * s3-mirror /usr/local/bin/lock-wrapper s3sync-main /usr/local/bin/s3.sh
2>&1 | /usr/local/bin/nag-once s3.sh 1d
2>&1
Second, the attached patch changes the sync scripts to:
* do one sync with no --delete and excluding repodata
* do another one with --delete and including repodata
* invalidate the repodata
I adjusted the cron jobs to handle the repodata invalidate (I think).
TODO: only sync when things have changed.
+1s?
kevin
--