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

Li Lu commented on YARN-3034:
-----------------------------

bq. For the DistributedShell from Junping Du's comment, i thought Junping 
wanted in the existing way, Junping can you confirm based on it i can do the 
required modifications for DistributedShell
I understand that this patch is fine with our current DistributedShell design, 
and also fine with the tests in TestDistributed shell. I'm OK to have the patch 
in here. 

As a further clarification, my problem is mainly on the test distributed shell. 
Right now we're using very ad hoc ways to set which version of timeline service 
we're using. Currently we're using test names to distinguish timeline V1 and 
V2, and since both versions work on the same port, we need to explicitly 
disable one version to use the other. Instead of doing this in the test script 
each time, I'd hope that there are some global settings/logic on the server 
side to decide which exact version of timeline service to launch. All the tests 
need to do is to check (and set) the version of active timeline service and 
launch the mini YARN cluster. It's a little bit off topic here so let move the 
rest discussion to YARN-3352. 

> [Aggregator wireup] Implement RM starting its ATS writer
> --------------------------------------------------------
>
>                 Key: YARN-3034
>                 URL: https://issues.apache.org/jira/browse/YARN-3034
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3034-20150312-1.patch, YARN-3034.20150205-1.patch, 
> YARN-3034.20150316-1.patch
>
>
> Per design in YARN-2928, implement resource managers starting their own ATS 
> writers.



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

Reply via email to