[
https://issues.apache.org/jira/browse/MAPREDUCE-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183480#comment-15183480
]
Naganarasimha G R commented on MAPREDUCE-6546:
----------------------------------------------
Thanks [~sjlee0] for the latest patch few more nits :
# Its better to capture the defaults for {{timeline service version}} and
{{-mtype}}
# {{\[-d <path>\] root path of job history files}} => {{\[-d <path>\] hdfs root
path of job history fileS}}
# I had configured for V2(ATS) and when submitting a job missed to specify
{{-v}} option, job succeeded with counter stats as
{code}
org.apache.hadoop.mapreduce.TimelineServicePerformance$PerfCounters
TIMELINE_SERVICE_WRITE_COUNTER=100
TIMELINE_SERVICE_WRITE_FAILURES=100
TIMELINE_SERVICE_WRITE_KBS=100
TIMELINE_SERVICE_WRITE_TIME=13
File Input Format Counters
Bytes Read=0
File Output Format Counters
Bytes Written=0
TRANSACTION RATE (per mapper): 7692.307692307692 ops/s
IO RATE (per mapper): 7692.307692307692 KB/s
TRANSACTION RATE (total): 7692.307692307692 ops/s
IO RATE (total): 7692.307692307692 KB/s
{code}
So wondering whether we can add a check to confirm \#failures is != write
counters before declaring it as success when {{-mtype}} option is 1 ?
Apart from this ran it for all V2 options and its running fine.
> reconcile the two versions of the timeline service performance tests
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-6546
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6546
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Minor
> Labels: yarn-2928-1st-milestone
> Attachments: MAPREDUCE-6546-YARN-2928.01.patch,
> MAPREDUCE-6546-YARN-2928.02.patch
>
>
> The trunk now has a version of the timeline service performance test
> (YARN-2556). The timeline service v.2 (YARN-2928) also has a performance
> test, and these two versions are quite similar (by design).
> We need to reconcile the two.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
