Zhijie Shen commented on YARN-2854:

[~Naganarasimha], thanks of taking this documentation work. I suggest doing the 
following updates:

1. If you read through the document, the per-framework data (which is actually 
the basic timeline service) and the generic data (aka the generic history 
service) sound two equal pieces in this daemon. It may be better to promote the 
timeline service as the first-class citizen of this document, and then explain 
the generic history service as the build-in payload of it.

2. We need to update the current status section. Up till now, the essential 
functionality of the timeline server is done, and it can work in both insecure 
and secure modes. The generic history service has already ridden on the 
timeline store. The coming thing may be the scalability and reliability of the 
timeline service. As the target fix version is set to 2.7.0. We may update it 
around the end of the release.

2. Add a section about enabling security of the timeline server. I can help 
with this section if necessary.

3. The configurations about the generic history service needs to be updated.

4. It may be better to enhance the client example code, at least to show how to 
create a domain, and put the entity into a particular domain.

5. For the API specifications, let's still keep it separately: YARN-1876

> The document about timeline service and generic service needs to be updated
> ---------------------------------------------------------------------------
>                 Key: YARN-2854
>                 URL: https://issues.apache.org/jira/browse/YARN-2854
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Naganarasimha G R
>            Priority: Critical
>         Attachments: YARN-2854.20141120-1.patch

This message was sent by Atlassian JIRA

Reply via email to