[jira] [Created] (AMBARI-22553) When Namenode HA is enabled and the default port for namenode is changed, quicklinks does not reflect the changed port

["Amine ZITOUNI (JIRA)" <ji...@apache.org>]

Amine ZITOUNI created AMBARI-22553:
--------------------------------------

             Summary: When Namenode HA is enabled and the default port for namenode is changed, quicklinks does not reflect the changed port
                 Key: AMBARI-22553
                 URL: https://issues.apache.org/jira/browse/AMBARI-22553
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.2
            Reporter: Amine ZITOUNI
            Priority: Minor


I changed Yarn, HBase, Spark... quick links default ports .The quick links are working fine. But there is an issue when changing HDFS quick links port.

On my conf I changed the following properties:

from

"dfs.namenode.http-address": "myIP:50700",
"dfs.namenode.http-address.mycluster.namenode1": "myIP:50700",
"dfs.namenode.http-address. mycluster.namenode2": "myIP:50700"

to

"dfs.namenode.http-address": "myIP:MyNewPort",
"dfs.namenode.http-address. mycluster.namenode1": "myIP: MyNewPort",
"dfs.namenode.http-address. mycluster.namenode2": "myIP: MyNewPort"

but HDFS quick links still uses port 50700.

The workaround is to substitute the new port on HDFS quicklinks.json file before starting Ambari Server:

sed -i "s?50070?MyNewPort?" /var/lib/ambari-server/resources/stacks/HDP/2.3/services/HDFS/quicklinks/quicklinks.json

For more details please see follow this link :
https://community.hortonworks.com/questions/149232/hdfs-quicklinks-not-using-port-set-on-blueprints-c.html?childToView=149749#answer-149749



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)