question Re: Yarn Web Interface reporting '0' for many metrics for successfully completed applications. in Archives of Support Questions (Read Only)

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

prsingh1 — Mon, 27 Mar 2017 16:58:19 GMT

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 

}

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

nyadav — Mon, 27 Mar 2017 17:13:03 GMT

@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

yarn.scheduler.capacity.root.acl_administer_jobs=*  

yarn.scheduler.capacity.root.acl_administer_queue=*

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

prsingh1 — Mon, 27 Mar 2017 17:31:31 GMT

@nyadav

Setting the root.acl properties resolved the issue.