From 7cc5c16ab97727211d68c34130710ef41e524dbb Mon Sep 17 00:00:00 2001 From: guyben Date: Fri, 24 May 2019 07:31:17 -0700 Subject: [PATCH] Increase delay between attempts of rde staging Our database is big enough now that it takes > 4 hours to run the RDE Staging mapreduce. Retrying after 4 hours just causes a new mapreduce to run, interfering with the old one. 8 hours still means 3 attempts per 24 hour period (00:07, 08:07, 16:07) so we can catch up with the cursor if needed. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=249829914 --- java/google/registry/env/production/default/WEB-INF/cron.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/google/registry/env/production/default/WEB-INF/cron.xml b/java/google/registry/env/production/default/WEB-INF/cron.xml index 068c8f988..e1543d310 100644 --- a/java/google/registry/env/production/default/WEB-INF/cron.xml +++ b/java/google/registry/env/production/default/WEB-INF/cron.xml @@ -32,7 +32,7 @@ we add a 4+ minute grace period to ensure the transactions cool down, since our queries are not transactional. --> - every 4 hours from 00:07 to 20:00 + every 8 hours from 00:07 to 20:00 backend