YARN-8616. systemClock should be used in RMAppImpl instead of System.currentTimeMills(), to be consistent. (Contributed by Szilard Nemeth)

This commit is contained in:
Haibo Chen 2018-09-24 16:02:57 -07:00
parent cf62ff9a6a
commit 29dad7d258
1 changed files with 3 additions and 3 deletions

View File

@ -1507,7 +1507,7 @@ public class RMAppImpl implements RMApp, Recoverable {
}
public void transition(RMAppImpl app, RMAppEvent event) {
app.logAggregationStartTime = System.currentTimeMillis();
app.logAggregationStartTime = app.systemClock.getTime();
for (NodeId nodeId : app.getRanNodes()) {
app.handler.handle(
new RMNodeCleanAppEvent(nodeId, app.applicationId));
@ -1767,7 +1767,7 @@ public class RMAppImpl implements RMApp, Recoverable {
try {
this.readLock.lock();
if (!isLogAggregationFinished() && isAppInFinalState(this) &&
System.currentTimeMillis() > this.logAggregationStartTime
systemClock.getTime() > this.logAggregationStartTime
+ this.logAggregationStatusTimeout) {
for (Entry<NodeId, LogAggregationReport> output :
logAggregationStatus.entrySet()) {
@ -2060,7 +2060,7 @@ public class RMAppImpl implements RMApp, Recoverable {
String appViewACLs = submissionContext.getAMContainerSpec()
.getApplicationACLs().get(ApplicationAccessType.VIEW_APP);
rmContext.getSystemMetricsPublisher().appACLsUpdated(
this, appViewACLs, System.currentTimeMillis());
this, appViewACLs, systemClock.getTime());
}
@Private