[ https://issues.apache.org/jira/browse/YARN-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335409#comment-16335409 ]
Rohith Sharma K S commented on YARN-3895: ----------------------------------------- {quote}I could see cases where the ACLs are not that small, potentially larger than an average entity. {quote} I am wondering when this could happen? How much big would be ACL's size?. This can be limited to some bytes per entity. In similar situation in MR/Native service AM while publishing AM configurations, we restrict per entity object to configurable bytes. I think clients should use this methods while publishing entities. {quote}Just as that would be cumbersome to store per cell, it would be cumbersome to build and parse per entity. {quote} The ACLs details need to sent one time per entity-id. ACLs object will contains only reader details which is similar to TimelineDomain#reader field. Any update for entity-id need not to send acls details again. Further, any update on ACLs can send later as well but either older one will be overwritten or can be appended which we can decide it. Sending ACLs info one time per entity-id makes bigger impact? From Hbase, storing it in column shouldn't be much issue. Benefit we get is we can apply substring filter when acls is enabled in Hbase. > Support ACLs in ATSv2 > --------------------- > > Key: YARN-3895 > URL: https://issues.apache.org/jira/browse/YARN-3895 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Affects Versions: YARN-2928 > Reporter: Varun Saxena > Assignee: Varun Saxena > Priority: Major > Labels: YARN-5355 > > This JIRA is to keep track of authorization support design discussions for > both readers and collectors. -- 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