Yarn Web Interface reporting '0' for many metrics for successfully completed applications.

[#1]

Yarn Web Interface reporting '0' for many metrics for successfully completed applications.

{ 

"id": "application_1480114771287_15299", 

"user": "xx", 

"name": "usr", 

"queue": "default", 

"state": "FINISHED", 

"finalStatus": "SUCCEEDED", 

"progress": 100, 

"trackingUI": "History", 

"trackingUrl": "http://<HOST>:8088/proxy/application_1480114771287_15299/", 

"diagnostics": "", 

"clusterId": 1480114771287, 

"applicationType": "MAPREDUCE", 

"applicationTags": "", 

"startedTime": 0, 

"finishedTime": 0, 

"elapsedTime": 0, 

"allocatedMB": 0, 

"allocatedVCores": 0, 

"runningContainers": 0, 

"memorySeconds": 172160, 

"vcoreSeconds": 49, 

"queueUsagePercentage": 0, 

"clusterUsagePercentage": 0, 

"preemptedResourceMB": 0, 

"preemptedResourceVCores": 0, 

"numNonAMContainerPreempted": 0, 

"numAMContainerPreempted": 0 

} 

[#2 · Accepted solution]

@prsingh

When RM UI is Kerberized, only the admin / job user can view the startedTime, finishedTime, elapsedTime and amContainerLogs on using the RM web service. To enable access for other users, we can either set

yarn.admin.acl = false 

or

yarn.scheduler.capacity.root.acl_administer_jobs=*  

yarn.scheduler.capacity.root.acl_administer_queue=*

[#3]

@nyadav

Setting the root.acl properties resolved the issue.