Vinod Kumar Vavilapalli commented on YARN-3293:

+1 for doing this.

We do not need to be specific to any scheduler.

Had an offline discussion with [~vvasudev] and [~venkateshrin]. Here are a few 
things worth highlighting
 - Last Scheduling Cycle: Timestamp, Allocated Resource (MB, VCores), Reserved 
Resource, Released Resource
 - Number of Allocations so far
 - Last Allocation: Timestamp, Node, Container, Queue
 - Number of Resource releases so far
 - Last Resource Release: Timestamp, Container, Queue
 - Number of Preemptions so far
 - Last Preemption: Timestamp, Container, Queue
 - Number of fulfilled reservations so far. Fulfilled reservations do not 
include our internal (unreserve + reserve) operations
 - Last Reservation: Timestamp, Node, Container, Queue
 - Others: Maximum current node size (MB, Cores) in the cluster
 - Configuration: Cluster level Minimum Allocation MB, Maximum Allocation MB, 
similar values for cores

> Track and display capacity scheduler health metrics in web UI
> -------------------------------------------------------------
>                 Key: YARN-3293
>                 URL: https://issues.apache.org/jira/browse/YARN-3293
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
> It would be good to display metrics that let users know about the health of 
> the capacity scheduler in the web UI. Today it is hard to get an idea if the 
> capacity scheduler is functioning correctly. Metrics such as the time for the 
> last allocation, etc.

This message was sent by Atlassian JIRA

Reply via email to