Li Lu commented on YARN-4234:

I think here are some miscommunications, please feel free to correct me if I'm 
wrong. Here are actually two problems we're discussing:
- For ATS v1.5 entity write patch, the client should not contact the server. In 
this way we're offloading the traffic from the centralized server, which became 
a significant problem of ATS v1. 
- For ATS compatibility issue raised in YARN-4183, we need to come up a 
mechanism to let the clients and server coordinate. Specifically, the client 
may want to know the server's ATS version or where exactly it needs to write 
the timeline entities. Client side configurations may not be consistent with 
the server in this case. So, maybe we want some mechanisms to coordinate on 

Not sure if I got the points right but to me those two points are independent? 

> New put APIs in TimelineClient for ats v1.5
> -------------------------------------------
>                 Key: YARN-4234
>                 URL: https://issues.apache.org/jira/browse/YARN-4234
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-4234.1.patch, YARN-4234.2.patch, 
> YARN-4234.20151109.patch, YARN-4234.20151110.1.patch, 
> YARN-4234.20151111.1.patch, YARN-4234.3.patch
> In this ticket, we will add new put APIs in timelineClient to let 
> clients/applications have the option to use ATS v1.5

This message was sent by Atlassian JIRA

Reply via email to