big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
Change-Id: I2567f4669ad868e13c4301fe44c4bde85bb92c37
This commit is contained in:
Wangda Tan 2018-03-26 11:20:16 -07:00
parent 9eef19b2ad
commit 24bc5e0e4d
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
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
View File

@ -184,8 +184,10 @@ public Map<Set<String>, PlacementConstraint> getConstraints(
try {
readLock.lock();
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);
}
return null;
}
@ -213,8 +215,10 @@ public PlacementConstraint getConstraint(ApplicationId appId,
try {
readLock.lock();
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);
}
return null;
}
// TODO: Merge this constraint with the global one for this tag, if one