Support Questions
Find answers, ask questions, and share your expertise

HDFS quicklinks not using port set on blueprints conf

HDFS quicklinks not using port set on blueprints conf

New Contributor

Hello,

I’m using Apache Ambari.

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

Thanks a lot in advance for your feedbacks.

Best Regards,

Amine

4 REPLIES 4

Re: HDFS quicklinks not using port set on blueprints conf

Expert Contributor
@Amine ZITOUNI

can you please let us know the release version of Apache Ambari that you are using ?

Re: HDFS quicklinks not using port set on blueprints conf

New Contributor

Version 2.5.2.0

Re: HDFS quicklinks not using port set on blueprints conf

Expert Contributor

Thanks for the information @Amine ZITOUNI

I was able to confirm that this is an existing issue in ambari since version 2.2.2

When Namenode HA is enabled and the default port for namenode is changed, quicklinks does not reflect the changed port

Please report this as ambari bug at https://issues.apache.org/jira/projects/AMBARI and inform us on this thread. We will look to address this issue in upcoming version of ambari

Re: HDFS quicklinks not using port set on blueprints conf

New Contributor

Thanks!

The bug has been reported : https://issues.apache.org/jira/browse/AMBARI-22553