YARN-8072. RM log is getting flooded with MemoryPlacementConstraintManager info logs. (Zian Chen via wangda)

Change-Id: I2567f4669ad868e13c4301fe44c4bde85bb92c37

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/constraint/MemoryPlacementConstraintManager.java

@@ -184,8 +184,10 @@ public class MemoryPlacementConstraintManager
     try {
       readLock.lock();
       if (appConstraints.get(appId) == null) {
-        LOG.info("Application {} is not registered in the Placement "
-            + "Constraint Manager.", appId);
+        if (LOG.isDebugEnabled()) {
+          LOG.debug("Application {} is not registered in the Placement "
+              + "Constraint Manager.", appId);
+        }
         return null;
       }
 
@@ -213,8 +215,10 @@ public class MemoryPlacementConstraintManager
     try {
       readLock.lock();
       if (appConstraints.get(appId) == null) {
-        LOG.info("Application {} is not registered in the Placement "
-            + "Constraint Manager.", appId);
+        if (LOG.isDebugEnabled()) {
+          LOG.debug("Application {} is not registered in the Placement "
+              + "Constraint Manager.", appId);
+        }
         return null;
       }
       // TODO: Merge this constraint with the global one for this tag, if one