You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Phil Zampino (JIRA)" <ji...@apache.org> on 2018/04/23 13:46:00 UTC

[jira] [Commented] (KNOX-1268) [Service Discovery] On a wire encrypted cluster , HDFSUI and WEBHDFS service url is getting updated with wrong port

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

Phil Zampino commented on KNOX-1268:
------------------------------------

The dfs.https.port property isn't used directly by discovery, but it is accurate to say that the https-related address properties are not currently being referenced.

> [Service Discovery] On a wire encrypted cluster , HDFSUI and WEBHDFS service url is getting updated with wrong port
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: KNOX-1268
>                 URL: https://issues.apache.org/jira/browse/KNOX-1268
>             Project: Apache Knox
>          Issue Type: Bug
>    Affects Versions: 0.14.0
>            Reporter: J.Andreina
>            Assignee: Phil Zampino
>            Priority: Critical
>             Fix For: 1.1.0
>
>
> On a wire encrypted cluster , HDFS url is getting updated with wrong port
> Expected HDFS urls in generated topology : 
>  [https://host1:20470|https://host1:20470/]
>  [https://host2:20470|https://host2:20470/]
> Actual:
> {noformat}
>  <service>
>  <role>WEBHDFS</role>
>  <url>https:/host1:20070/webhdfs</url>
>  <url>https://host2:20070/webhdfs</url>
>  </service>
>  <service>
>  <role>HDFSUI</role>
>  <url>https://host1:20070</url>
>  <url>https://host2:20070</url>
>  </service>
> {noformat}
> Should fetch port value using config "dfs.https.port" from hdfs-site.xml



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)