Thanks @Namit Maheshwari @rguruvannagari We managed to solve our problem with your help. I'll explain what we did to make the installation successful, if it can help someone.
In the end, it has nothing to do with the Linux distro or the hardware (IBM Power) but the issue was the default configuration for HDFS. First, we deleted by hand every directory that is not /usr/hdp/2.6.0.x-xxxx/, /usr/hdp/current/, and /usr/hdp/share/. Everything that look like a service directory. Our problem was that we had
a /usr/hdp/hadoop/ directory that should not have been there, without understanding why the installation process created it. Second, we changed the HDFS configurations for the NameNode directories and the DataNodes directories. During the installation process, Amabri set up these default paths where we can see our culprit in the NameNode directories: /usr/hdp/hadoop. That's probably why the installation script create this directory, because it's defined in the configuration file. We keep only the local FS /hadoop/hdfs/namenode/ directory for the NameNode (we could have add another one from the network storage but we don't have network storage). We also added our 12 disks per nodes paths for the DataNode directories and deleted the others. I'm just surprised that Ambari will propose "faulty" directories as default, but heh, I guess it's not perfect and you still need to know what you're doing! In the end, the installation process for the NameNodes went through, as the other services. Thanks again,
François
... View more
