From 9e9915ddab7ff79224b075889f67c38920fde9f0 Mon Sep 17 00:00:00 2001
From: Nanda kumar <nanda@apache.org>
Date: Tue, 9 Oct 2018 18:23:05 +0530
Subject: [PATCH] HDDS-599. Fix TestOzoneConfiguration
 TestOzoneConfigurationFields. Contributed by Sandeep Nemuri.

---
 .../src/main/resources/ozone-default.xml      | 21 -------------------
 1 file changed, 21 deletions(-)

diff --git a/hadoop-hdds/common/src/main/resources/ozone-default.xml b/hadoop-hdds/common/src/main/resources/ozone-default.xml
index d7cbd75b6b..aee471e9b8 100644
--- a/hadoop-hdds/common/src/main/resources/ozone-default.xml
+++ b/hadoop-hdds/common/src/main/resources/ozone-default.xml
@@ -1105,27 +1105,6 @@
     </description>
   </property>
 
-  <property>
-    <name>hdds.write.lock.reporting.threshold.ms</name>
-    <value>5000</value>
-    <tag>OZONE, DATANODE, MANAGEMENT</tag>
-    <description>
-      When a write lock is held for a long time, this will be logged as the
-      lock is released. This sets how long the lock must be held for logging
-      to occur.
-    </description>
-  </property>
-
-  <property>
-    <name>hdds.lock.suppress.warning.interval.ms</name>
-    <value>10000</value>
-    <tag>OZONE, DATANODE, MANAGEMENT</tag>
-    <description>
-      Instrumentation reporting long critical sections will suppress
-      consecutive warnings within this interval.
-    </description>
-  </property>
-
   <property>
     <name>hdds.command.status.report.interval</name>
     <value>30s</value>