#Hortonworks #Community Nobody helped me, but I found the solution and I think they should add it to the manual of Rolling back namenodeha in the section #modify_hdfs_configurations since the manual is not clear in some things. The next command to get hdfs configurations. # /var/lib/ambari-server/resources/scripts/configs.py -u <AMBARI_USER> -p <AMBARI_PW> -port <AMBARI_PORT> get localhost <CLUSTER_NAME> hdfs-site Before you start change the parameters with yours, the commands was in my case. If you have the next line, delete it since points to namenodeha. "dfs.internal.nameservices" and you delete with the next command. # /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 8080 delete localhost BigDataCenter hdfs-site dfs.internal.nameservices Now you find this lines and delete it, if you find the same lines but with "http" also delete it. "dfs.namenode.https-address.namenodeha.nn1" "dfs.namenode.https-address.namenodeha.nn2" # /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 8080 delete localhost BigDataCenter hdfs-site dfs.namenode.https-address.namenodeha.nn1 # /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 8080 delete localhost BigDataCenter hdfs-site dfs.namenode.https-address.namenodeha.nn2 You need to add the next lines since instead of pointing to namenodeha, you have to point to the namenode and add the next lines: "dfs.namenode.http-address" "<namenode>:<port>" "dfs.namenode.https-address" "<namenode>:<port>" # /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 8080 set localhost BigDataCenter hdfs-site dfs.namenode.http-address "master.root.com.mx:50070" # /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 8080 set localhost BigDataCenter hdfs-site dfs.namenode.https-address "master.root.com.mx:50470" and now the cluster works. you can start the services, first start hdfs and then the others. ... View more

The connection test works but i fix the error only drop the database ranger, thank you for the answer. ... View more

Ya quedo resuelto el problema, tuve que reinstalar los paquetes de Ranger manualmente, yum search ranger y reinstall algunos paquetes, al volver a tirar tus comandos ya me aparecia credentialbuilder, pero me aparecia un error de que no podia ejecutar Mkdir en una ruta, cuando aparece la ruta quise acceder a ella, pero me genero errores de enlaces simbolicos duplicados, rastreando los archivos a donde apuntaban, los elimine, reinstale Ranger y funciono. Muchas Gracias, tu respuesta me dio la idea. ... View more