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

Change-Id: I2567f4669ad868e13c4301fe44c4bde85bb92c37
(cherry picked from commit 24bc5e0e4d)
This commit is contained in:
Wangda Tan 2018-03-26 11:20:16 -07:00
parent 62b9537332
commit dc99611878
1 changed files with 8 additions and 4 deletions

View File

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