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

Oleg Nechiporenko commented on AMBARI-7035:
-------------------------------------------

+1 for patch.

> Views: Jobs view support for existing ATS
> -----------------------------------------
>
>                 Key: AMBARI-7035
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7035
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.7.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7035.patch
>
>
> Add an optional instance parameter so an AMBARI.ADMIN can configure the view 
> to point to an existing / arbitrary ATS host and ResourceManager host.
> {code}
> <parameter>
>     <name>yarn.ats.url</name>
>     <description>The URL to the YARN Application Timeline Server, used to 
> provide Jobs information, typically, this is the 
> yarn.timeline-service.webapp.address property in the yarn-site.xml 
> configuration. For example: http://yarn.ats.address:8188</description>
>     <required>false</required>
> </parameter>
>   <parameter>
>       <name>yarn.resourcemanager.url</name>
>       <description>The URL to the YARN ResourceManager, used to provide YARN 
> Application data. For example: 
> http://yarn.resourcemanager.address:8088</description>
>       <required>false</required>
>   </parameter>
> {code}
> If these parameters are not set, the view should work as it does today 
> (assumes ambari server hosting this view has the cluster to obtain ATS, and 
> it gets that info from the Ambari REST API, and goes thru the ambari server 
> proxy to retrieve info from ATS).
> If these parameter are set, the view should just use this prop and the ambari 
> server proxy to retrieve info from ATS).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to