Can't install with Ambari 2.5+

[adamresson]

I tried upgrading to a newer version of Ambari (2.5 or 2.6) and every time my HDFS NameNode ends up failing.

It turns out, the problem ends up being with the default configuration recommendation provided by ambari, it sets the namenode directory to /mnt/pd1/hadoop/hdfs/namenode,/hadoop/hdfs/namenode which is two directories, but really the same directory since /hadoop is just a symlink to /mnt/pd1/hadoop. Therefore, when NameNode starts up, it tries to 'lock' the directory twice, but can't, since it sees itself as already having locked it.

I've deployed Ambari using the ambari_manual environment instead (where it just deploys ambari, and no services). This works initially, but when you go to install HDFS (unless you manually change the config) you get the same problem.

[adamresson]

Here's a quick env file if anyone wants to give this a try

AMBARI_VERSION='2.5.1.0'
import_env ./platforms/hdp/ambari_manual_env.sh

Then setup your SOCKS proxy, and try and go install HDFS service through the UI. You'll notice when you get to the config section, the NameNode and DataNode dirs have those duplicate entries.

[karth295]

I ran into this issue too, and I believe you can change those properties in platforms/hdp/configuration.json and continue using auto mode.