From d0c73efac05a502a5f7e8ba12d17bc3afd0f6f89 Mon Sep 17 00:00:00 2001 From: mcilwain Date: Wed, 9 Jan 2019 11:22:17 -0800 Subject: [PATCH] Reduce logging level to warning for missing DAIs This is expected as part of the normal way that this mapreduce runs, so it's not worth outputting an error. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=228553579 --- .../tools/server/KillAllDomainApplicationsAction.java | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/java/google/registry/tools/server/KillAllDomainApplicationsAction.java b/java/google/registry/tools/server/KillAllDomainApplicationsAction.java index 0c9673b20..f704c4ddc 100644 --- a/java/google/registry/tools/server/KillAllDomainApplicationsAction.java +++ b/java/google/registry/tools/server/KillAllDomainApplicationsAction.java @@ -82,8 +82,13 @@ public class KillAllDomainApplicationsAction implements Runnable { EppResourceIndex eri = ofy().load().entity(EppResourceIndex.create(applicationKey)).now(); + // This case is common and happens when the same domain name was applied for + // multiple times (i.e. there are multiple domain applications sharing a name). The + // first one that the mapreduce happens to process will delete the DAI and then + // subsequent ones will see the entity as already deleted, which is safe and + // expected. if (dai == null) { - logger.atSevere().log( + logger.atWarning().log( "Missing domain application index for application %s.", applicationKey); getContext().incrementCounter("missing domain application indexes"); } else {