You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Haibo Chen (JIRA)" <ji...@apache.org> on 2018/03/26 20:24:00 UTC
[jira] [Commented] (YARN-7932) [atsv2 read acls] Add a API
TimelineV2Client#putDomain to publish domain information.
[ https://issues.apache.org/jira/browse/YARN-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414473#comment-16414473 ]
Haibo Chen commented on YARN-7932:
----------------------------------
From a client's perspective, what needs to be supported first is TimelineV2Client API provide an API to write a TimelineDomain and then refer to it by its id. Writing to the backend and reading it upon TimelineCollector restart is for fault tolerance, internal to ATSv2.
In that sense, I'd argue that we should do TimelineV2Client API and TimelineCollector storing the domains in memory first. The timelinewriter.putDomain() and the timeinereader.readDomain() shall be done together to persist TimelineDomains. This Jira seems to be a good place to do the in-memeory storage of timelineDomains in TimelineCollector.
> [atsv2 read acls] Add a API TimelineV2Client#putDomain to publish domain information.
> -------------------------------------------------------------------------------------
>
> Key: YARN-7932
> URL: https://issues.apache.org/jira/browse/YARN-7932
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vrushali C
> Assignee: Rohith Sharma K S
> Priority: Major
> Attachments: YARN-7932.001.patch
>
>
>
> Need to have a TimelineDomain class in atsv2 that can contain the acls info for entities. TimelineEntity will contain TimelineDomain as a member
--
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