[ https://issues.apache.org/jira/browse/YARN-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405268#comment-16405268 ]
Haibo Chen commented on YARN-6936: ---------------------------------- [~rohithsharma]. Can you elaborate on why we want to expose the decision in client side configuration? It is a binary decision in this patch, but I think some frameworks may want to post both application entities and subapplication entities. What do you think if we provide two endpoints in TimelineCollectorWebServices, one for application and the other 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 > > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org