You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Sreenath Somarajapuram (JIRA)" <ji...@apache.org> on 2016/02/06 17:41:39 UTC

[jira] [Updated] (AMBARI-14951) Tez Ambari View: Add protocol configuration for YARN

     [ https://issues.apache.org/jira/browse/AMBARI-14951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sreenath Somarajapuram updated AMBARI-14951:
--------------------------------------------
    Description: 
- Value set in yarn.http.policy is required for creating task attempt log links, and we need a mechanism to get that configuration value at the UI side.
- As host points to Ambari proxy, there is no way to know the protocol at which yarn daemons are configured to run. 


  was:
- Currently host for rm and timeline is obtained from window.location.origin. As the support for origin is limited to modern browsers its better to construct the value from location.protocol, location.hostName & location.port.
- As host points to Ambari proxy, there is no way to know the protocol at which yarn daemons are configured to run. Value set in yarn.http.policy is required for creating task attempt log links, and we need a mechanism to get that configuration value at the UI side.



> Tez Ambari View: Add protocol configuration for YARN
> ----------------------------------------------------
>
>                 Key: AMBARI-14951
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14951
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>
> - Value set in yarn.http.policy is required for creating task attempt log links, and we need a mechanism to get that configuration value at the UI side.
> - As host points to Ambari proxy, there is no way to know the protocol at which yarn daemons are configured to run. 



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