[2212] added log for completion of load zone

diff --git a/src/bin/auth/auth_messages.mes b/src/bin/auth/auth_messages.mes
index a87c50e9480ab89f78b0b5fba3bdab697579675c..38b431c6e8d83d75d9bce5008f704165253d8b27 100644 (file)
--- a/src/bin/auth/auth_messages.mes
+++ b/src/bin/auth/auth_messages.mes
@@ -358,3 +358,8 @@ or temporary DB connection failure.  So the event is just logged and the
 thread keeps running.  In some rare cases, however, this may indicate
 an internal bug and it may be better to restart the entire program.
 So the log message should be carefully examined.
+
+% AUTH_DATASRC_CLIENTS_BUILDER_LOAD_ZONE loaded zone %1/%2
+This debug message is issued when the separate thread for maintaining data
+source clients successfully loaded the named zone of the named class as a
+result of the 'loadzone' command.

diff --git a/src/bin/auth/datasrc_clients_mgr.h b/src/bin/auth/datasrc_clients_mgr.h
index e7a2048db9779f9a6ec1a848d4403cad1dc26bf5..0392dd6de976f7063efc77a3acf3b73b1f5db89e 100644 (file)
--- a/src/bin/auth/datasrc_clients_mgr.h
+++ b/src/bin/auth/datasrc_clients_mgr.h
@@ -516,8 +516,9 @@ DataSrcClientsBuilderBase<MutexType, CondVarType>::doLoadZone(
     switch (result) {
     case datasrc::ConfigurableClientList::ZONE_RELOADED:
         // Everything worked fine.
-        //LOG_DEBUG(auth_logger, DBG_AUTH_OPS, AUTH_LOAD_ZONE)
-        //  .arg(zone_class).arg(origin);
+        LOG_DEBUG(auth_logger, DBG_AUTH_OPS,
+                  AUTH_DATASRC_CLIENTS_BUILDER_LOAD_ZONE)
+            .arg(origin).arg(rrclass);
         break;
     case datasrc::ConfigurableClientList::ZONE_NOT_FOUND:
         isc_throw(InternalCommandError, "failed to load zone " << origin