[ 
https://issues.apache.org/jira/browse/YARN-9538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011477#comment-17011477
 ] 

Weiwei Yang commented on YARN-9538:
-----------------------------------

Hi [~Tao Yang]

Few comments

CS
 # The newly added document should be  added to the table of content of the page
 # "Activities have been integrated into the application attempt page, should 
be shown below the table of outstanding requests when there is any outstanding 
request" -> "Activities info is available in the application attempt page on RM 
Web UI, where outstanding requests are aggregated and displayed.

 

RM

 

1. +The scheduler activities API currently supports Capacity Scheduler and 
provides a way to get scheduler activities in a single scheduling process, it 
will trigger recording scheduler activities in next scheduling process and then 
take last required scheduler activities from cache as the response. The 
response have hierarchical structure with multiple levels and important 
scheduling details which are organized by the sequence of scheduling process:

-> 

The scheduler activities Restful API can fetch scheduler activities info 
recorded in a scheduling cycle. The API returns a message that includes 
important scheduling activities info.

 

2. nodeId - specified node ID, if not specified, scheduler will record next 
scheduling process on any node.

->

specified node ID, if not specified, the scheduler will record the scheduling 
activities info for the next scheduling cycle on all nodes

 

+### Elements of the *Activities* object
+
+| Item | Data Type | Description |
+|:---- |:---- |:---- |
+| nodeId | string | The node ID on which scheduler tries to schedule 
containers. |
+| timestamp | long | Timestamp of the activities. |
+| dateTime | string | Date time of the activities. |
+| diagnostic | string | Top diagnostic of the activities about empty results, 
unavailable environments, or illegal input parameters, such as "waiting for 
display", "waiting for the next allocation", "Not Capacity Scheduler", "No node 
manager running in the cluster", "Got invalid groupBy: xx, valid groupBy types: 
DIAGNOSTICS" |
+| allocations | array of allocations | A collection of allocation objects. |
+

 

3. +| nodeId | string | The node ID on which scheduler tries to schedule 
containers. |

->

The node ID on which the scheduler tries to allocate containers.

 

4. +| diagnostic | string | Top diagnostic of the activities about empty 
results, unavailable environments, or illegal input parameters, such as 
"waiting for display", "waiting for the next allocation", "Not Capacity 
Scheduler", "No node manager running in the cluster", "Got invalid groupBy: xx, 
valid groupBy types: DIAGNOSTICS" |

Please remove "Not Capacity Scheduler".

 

5. Please replace all "ids" to "IDs"

 

6. four node activities will be separated into two groups

->

4 node activities info will be grouped into 2 groups.

 

7. + Application activities include useful scheduling info for a specified 
application, the response have hierarchical structure with multiple levels:

->

the response has a hierarchical layout with following fields:

 

8. * **AppActivities** - AppActivities are root structure of application 
activities within basic information.

->

is the root element?


9. +* **Applications** - Allocations are allocation attempts at app level 
queried from the cache.
->

shouldn't here be applications?

 

> Document scheduler/app activities and REST APIs
> -----------------------------------------------
>
>                 Key: YARN-9538
>                 URL: https://issues.apache.org/jira/browse/YARN-9538
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Tao Yang
>            Assignee: Tao Yang
>            Priority: Major
>         Attachments: YARN-9538.001.patch, YARN-9538.002.patch
>
>
> Add documentation for scheduler/app activities in CapacityScheduler.md and 
> ResourceManagerRest.md.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to