[
https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474759#comment-16474759
]
Haibo Chen commented on YARN-7933:
----------------------------------
If it's not in our design, I am inclined to remove it at this point in time.
{quote}Timeline Token verification is at filter layer at the time of http
connection establishment i.e even before it reaches servlets.
{quote}
Does that mean if two collectors are allocated on the same node, then one AM
can forge data of another? This is probably an independent issue that applies
to the other TimelineCollectorWebservices endpoint, putEntities(), which we
can address in another jira.
> [atsv2 read acls] Add TimelineWriter#writeDomain
> -------------------------------------------------
>
> Key: YARN-7933
> URL: https://issues.apache.org/jira/browse/YARN-7933
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vrushali C
> Assignee: Rohith Sharma K S
> Priority: Major
> Attachments: YARN-7933.01.patch, YARN-7933.02.patch,
> YARN-7933.03.patch, YARN-7933.04.patch, YARN-7933.05.patch
>
>
>
> Add an API TimelineWriter#writeDomain for writing the domain info
--
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
