hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-5174) several updates/corrections to timeline service documentation
Date Fri, 17 Jun 2016 20:15:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336833#comment-15336833
] 

Varun Saxena edited comment on YARN-5174 at 6/17/16 8:14 PM:
-------------------------------------------------------------

[~sjlee0], you had earlier said :
"I am not sure if we need to highlight the aggregation operation bit. "

The aggregation operation part is currently there in the document. 
So what we need to decide upon is can some metrics at the level of task or something semantically
similar be posted by application directly without aggregating them upto the level of application
? Or we assume they will aggregate it by themselves (in which case this part can be removed).
If we go with latter, this can probably be explicitly stated i.e. application can do the aggregation
of metrics from task upto the app level.
Say, in case of Spark on YARN, multiple spark executors will be launched (with each one executing
multiple tasks). This will not be an immediate use case though, if ever.


was (Author: varun_saxena):
[~sjlee0], you had earlier said :
"I am not sure if we need to highlight the aggregation operation bit. "

The aggregation operation part is currently there in the document. 
So what we need to decide upon is can some metrics at the level of task or something semantically
similar be posted by application directly without aggregating them upto the level of application
? Or we assume they will aggregate it by themselves (in which case this part can be removed).
If we go with latter, this can probably be explicitly stated.
Say, in case of Spark on YARN, multiple spark executors will be launched (with each one executing
multiple tasks). This will not be an immediate use case though, if ever.

> several updates/corrections to timeline service documentation
> -------------------------------------------------------------
>
>                 Key: YARN-5174
>                 URL: https://issues.apache.org/jira/browse/YARN-5174
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>              Labels: yarn-2928-1st-milestone
>         Attachments: Hierarchy.png, PublishingApplicationDatatoYARNTimelineServicev.pdf,
The YARN Timeline Service v.2.pdf, YARN-5174-YARN-2928.01.patch, YARN-5174-YARN-2928.02.patch,
YARN-5174-YARN-2928.03.patch, YARN-5174-YARN-2928.03.patch, YARN-5174-YARN-2928.04.patch,
YARN-5174-YARN-2928.05.patch, flow_hierarchy.png
>
>
> One part that is missing in the documentation is the need to add {{hbase-site.xml}} on
the client side (the client hadoop cluster). First, we need to arrive at the minimally required
client setting to connect to the right hbase cluster. Then, we need to document it so that
users know exactly what to do to configure the cluster to use the timeline service v.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message