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] [Updated] (YARN-5739) Provide timeline reader API to list available timeline entity types for one application
Date Tue, 22 Nov 2016 21:50:58 GMT

     [ https://issues.apache.org/jira/browse/YARN-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Li Lu updated YARN-5739:
------------------------
    Attachment: YARN-5739-YARN-5355.004.patch

Address comments above. 

bq. Moreover, REST endpoint suggestion was both entity-types and entitytypes. I am fine with
both as we do use hyphen in other REST endpoints in YARN. Let us go with majority opinion.

Right now I'm following our practices in node label related web services in the RM. Please
do let me know if the hyphens will cause any troubles. Thanks! 

> Provide timeline reader API to list available timeline entity types for one application
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-5739
>                 URL: https://issues.apache.org/jira/browse/YARN-5739
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Li Lu
>            Assignee: Li Lu
>         Attachments: YARN-5739-YARN-5355.001.patch, YARN-5739-YARN-5355.002.patch, YARN-5739-YARN-5355.003.patch,
YARN-5739-YARN-5355.004.patch
>
>
> Right now we only show a part of available timeline entity data in the new YARN UI. However,
some data (especially library specific data) are not possible to be queried out by the web
UI. It will be appealing for the UI to provide an "entity browser" for each YARN application.
Actually, simply dumping out available timeline entities (with proper pagination, of course)
would be pretty helpful for UI users. 
> On timeline side, we're not far away from this goal. Right now I believe the only thing
missing is to list all available entity types within one application. The challenge here is
that we're not storing this data for each application, but given this kind of call is relatively
rare (compare to writes and updates) we can perform some scanning during the read time. 



--
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