[
https://issues.apache.org/jira/browse/YARN-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022370#comment-16022370
]
Varun Saxena commented on YARN-3053:
------------------------------------
[~jlowe], sorry I was on a fairly long leave so did not see your message and
hence could not reply.
bq. I'm assuming the ATSv2 client is going to have to buffer/spool events
until the collector has been discovered or there's some kind of flow control
mitigation there.
Yes, there is an inbuilt mechanism to sleep and retry(based on configurations)
till we get the timeline service address.
Async entities will be directly put into a queue. And sync entity put will be
blocking until it is sent out from the client.
There is also a retry mechanism available in case any exception is encountered
while publishing entity to collector, possibly because collector has crashed.
> [Security] Review and implement authentication in ATS v.2
> ---------------------------------------------------------
>
> Key: YARN-3053
> URL: https://issues.apache.org/jira/browse/YARN-3053
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Labels: YARN-5355, yarn-5355-merge-blocker
> Attachments: ATSv2Authentication(draft).pdf,
> ATSv2Authentication.v01.pdf
>
>
> Per design in YARN-2928, we want to evaluate and review the system for
> security, and ensure proper security in the system.
> This includes proper authentication, token management, access control, and
> any other relevant security aspects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
