hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6936) [Atsv2] Retrospect storing entities into sub application table from client perspective
Date Fri, 30 Mar 2018 07:12:00 GMT

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

Rohith Sharma K S commented on YARN-6936:
-----------------------------------------

bq. Hence, I think we don't need to create another publisher just for SubApplication Entities.
We still need separate publisher because SubApplicationEntity will not contain any predefined
entity type rather it is user defined entity type unlike any other entities such as YARN_APPLICATION
and others. When entities are posted to TimelineCollectorWebService, TimelineEntities are
wrapped to corresponding Hierarchical entities which are predefined with entity type. But
for sub application entities are user defined entity types. So separate API's and publisher
in Timelinev2clientImpl is required to distinguish between normal entity and sub application
entities.  

> [Atsv2] Retrospect storing entities into sub application table from client perspective
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-6936
>                 URL: https://issues.apache.org/jira/browse/YARN-6936
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>            Priority: Major
>         Attachments: YARN-6936.000.patch, YARN-6936.001.patch
>
>
> Currently YARN-6734 stores entities into sub application table only if doAs user and
submitted users are different. This holds good for Tez kind of use cases. But AM runs as same
as submitted user like MR also need to store entities in sub application table so that it
could read entities without application id. 
> This would be a point of concern later stages when ATSv2 is deployed into production.
This JIRA is to retrospect decision of storing entities into sub application table based on
client side configuration driven rather than user driven. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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