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

Hitesh Shah commented on TEZ-3101:
----------------------------------

{code}
 //yarnProtocol - If specified, this protocol will be used to connect to 
construct node manager log links
{code}
  - the description does not mention how it should be specified, what the 
supported values are 

{code}
 url = urlParts[1] ? '%@?%@'.fmt(urlParts[0], urlParts[1]) : urlParts[0];
670     
671         if(url.indexOf("://") === -1 && protocol) {
672           url = "%@://%@".fmt(protocol, url);
673         }
674     
675         return url;
{code}
  - isnt there an inbuilt javascript library api that can be leveraged instead 
of the manual parsing? 

What happens if RMWebUrl is specified without a preceding http://? 

downloadUrl should not be changed in this path as it uses the configured 
property value of "yarn.log.server.url" and that should be configured correctly 
with the proper protocol. The http protocol policy should only be applied on in 
progress. 

Please clarify why the change in logs-cell.hbs is needed? 

 

  

> Tez UI: Task attempt log link doesn't have the correct protocol
> ---------------------------------------------------------------
>
>                 Key: TEZ-3101
>                 URL: https://issues.apache.org/jira/browse/TEZ-3101
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3101.1.patch
>
>
> - When inside ambari: Use protocol defined in yarn.http.policy configuration 
> to create the link. The value will be passed as a configuration by the Ambari 
> view code.
> - When running in standalone mode use the protocol in RM host URL.
> - Also ensure that the link is of the format 
> {code}http://foo.com:8042/node/containerlogs/<container_id>/<submitter>/syslog_<attempt_id>?user.name=<submitter>{code}



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

Reply via email to