YARN-3191. Log object should be initialized with its own class. Contributed by Rohith.

(cherry picked from commit 99c7f2b8fa417303e8f42ea3641c302135879280)
This commit is contained in:
Akira Ajisaka 2015-02-12 17:56:59 -08:00
parent a9a361c549
commit 9d8dbf8ea4
3 changed files with 5 additions and 2 deletions

View File

@ -546,6 +546,9 @@ Release 2.7.0 - UNRELEASED
YARN-3104. Fixed RM to not generate new AMRM tokens on every heartbeat
between rolling and activation. (Jason Lowe via jianhe)
YARN-3191. Log object should be initialized with its own class. (Rohith via
aajisaka)
Release 2.6.0 - 2014-11-18
INCOMPATIBLE CHANGES

View File

@ -73,7 +73,7 @@ public class ApplicationImpl implements Application {
private final WriteLock writeLock;
private final Context context;
private static final Log LOG = LogFactory.getLog(Application.class);
private static final Log LOG = LogFactory.getLog(ApplicationImpl.class);
private LogAggregationContext logAggregationContext;

View File

@ -99,7 +99,7 @@ public class ContainerImpl implements Container {
/** The NM-wide configuration - not specific to this container */
private final Configuration daemonConf;
private static final Log LOG = LogFactory.getLog(Container.class);
private static final Log LOG = LogFactory.getLog(ContainerImpl.class);
private final Map<LocalResourceRequest,List<String>> pendingResources =
new HashMap<LocalResourceRequest,List<String>>();
private final Map<Path,List<String>> localizedResources =