From db859e8172338a67c336dffa5fff95b618cd0fec Mon Sep 17 00:00:00 2001
From: Weiwei Yang <wwei@apache.org>
Date: Sun, 16 Jul 2017 22:40:20 +0800
Subject: [PATCH] HDFS-12148. Ozone: TestOzoneConfigurationFields is failing
 because ozone-default.xml has some missing properties. Contributed by Weiwei
 Yang.

---
 .../src/main/resources/ozone-default.xml      | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/ozone-default.xml b/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/ozone-default.xml
index cd444e9e959..bd29ce47fb5 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/ozone-default.xml
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/ozone-default.xml
@@ -327,6 +327,37 @@
     </description>
   </property>
 
+  <property>
+    <name>ozone.scm.max.container.report.threads</name>
+    <value>100</value>
+    <description>
+      Maximum number of threads to process container reports in scm.
+      Each container report from a datanode is processed by scm in
+      a worker thread, fetched from a thread pool. This property is
+      used to control the maximum size of the thread pool.
+    </description>
+  </property>
+
+  <property>
+    <name>ozone.scm.container.reports.wait.timeout.seconds</name>
+    <value>300</value>
+    <description>
+      Maximum time to wait in seconds for processing all container
+      reports from a node pool. It determines the timeout for a
+      node pool reports.
+    </description>
+  </property>
+
+  <property>
+    <name>ozone.scm.container.report.processing.interval.seconds</name>
+    <value>60</value>
+    <description>
+      Time interval in seconds for scm to process container reports
+      for a node pool. Scm handles node pool reports in a cyclic clock
+      manner, it fetches pools periodically with this time interval.
+    </description>
+  </property>
+
   <property>
     <name>dfs.container.ipc</name>
     <value>50011</value>