hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST
Date Thu, 08 Sep 2016 00:59:20 GMT

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

Li Lu commented on YARN-5561:
-----------------------------

OK I revisited the patch and our reader REST APIs. Right now we have 26 (!) APIs for reader
server. I tried to organize them in a way easier to understand:
{code}
0. cluster activity (2)
  - /flows/
  - /clusters/{clusterid}/flows/

1. (cluster - )user - flow - run - app - entity_type - entity_id sequence
  
  1.1 hierarchical (12)
  
    - /clusters/{clusterid}/users/{userid}/flows/{flowname}/runs/{flowrunid}/apps/
    - /clusters/{clusterid}/users/{userid}/flows/{flowname}/runs/{flowrunid}/
    - /clusters/{clusterid}/users/{userid}/flows/{flowname}/runs/
    - /users/{userid}/flows/{flowname}/runs/{flowrunid}/apps/
    - /users/{userid}/flows/{flowname}/runs/{flowrunid}/
    - /users/{userid}/flows/{flowname}/runs/
    
    (user, flow, run information omitted since an application is unique in a cluster)
    - /clusters/{clusterid}/apps/{appid}/entities/{entitytype}/{entityid}/
    - /clusters/{clusterid}/apps/{appid}/entities/{entitytype}
    - /apps/{appid}/entities/{entitytype}/{entityid}/
    - /apps/{appid}/entities/{entitytype}
  
    - /clusters/{clusterid}/users/{userid}/flows/{flowname}/apps/ (looks weird, jumping levels)
    - /users/{userid}/flows/{flowname}/apps/ (looks weird, jumping levels)
  
  1.2 uid (6)
  
    - /flow-uid/{uid}/runs/
    - /run-uid/{uid}/
    - /run-uid/{uid}/apps
    - /app-uid/{uid}/
    - /app-uid/{uid}/entities/{entitytype} (entity type looks weird)
    - /entity-uid/{uid}/
  
2. (cluster - )app - app_attempt - container sequence (6)

  - /clusters/{clusterid}/apps/{appid}/appattempts/{appattemptid}/containers
  - /clusters/{clusterid}/apps/{appid}/appattempts
  - /clusters/{clusterid}/apps/{appid}/
  - /apps/{appid}/appattempts/{appattemptid}/containers
  - /apps/{appid}/appattempts
  - /apps/{appid}/
  {code}

So the new addition looks fine to me. Do we want to reorganize the code in a way consistent
with this list? Right now the code seems to be a little bit messy. We can do it in this JIRA,
or we can open a new JIRA to reorganize these APIs and discuss the endpoints that marked as
weird? Thanks! 

> [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via
REST
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-5561
>                 URL: https://issues.apache.org/jira/browse/YARN-5561
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-5561.patch, YARN-5561.v0.patch
>
>
> ATSv2 model lacks retrieval of {{list-of-all-apps}}, {{list-of-all-app-attempts}} and
{{list-of-all-containers-per-attempt}} via REST API's. And also it is required to know about
all the entities in an applications.
> It is pretty much highly required these URLs for Web  UI.
> New REST URL would be 
> # GET {{/ws/v2/timeline/apps}}
> # GET {{/ws/v2/timeline/apps/\{app-id\}/appattempts}}.
> # GET {{/ws/v2/timeline/apps/\{app-id\}/appattempts/\{attempt-id\}/containers}}
> # GET {{/ws/v2/timeline/apps/\{app id\}/entities}} should display list of entities that
can be queried.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message