@Marek I tried my best to dug this issue for you. First of all I want to clear that this is not CDSW issue. This is the HDFS client configuration issue. I found some discrepancy: In the hdfs-site.xml file notice the dfs.ha.namenodes.[nameservice ID] section where you have declared the NN IDs as "namenode43,namenode57" which is causing the issue as indicated in the message. <property>
<name>dfs.ha.namenodes.namenodeHA</name>
<value>namenode43,namenode57</value>
</property> "Namenode for namenodeHA remains unresolved for ID namenode57. Check your hdfs-site.xml file to ensure namenodes are configured properly." So you should declare the IP or FQDN here because the session is not resolving this short name as there is no entry in the "/etc/hosts" file. Your "/etc/hosts" file is consist only below format: ---- RUN cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 IP address blc-control-02.novalocal IP address blc-control-01.novalocal 👆This format is not recommended the Network names should be configured as below: 1.1.1.1 foo-1.example.com foo-1
2.2.2.2 foo-2.example.com foo-2
3.3.3.3 foo-3.example.com foo-3
4.4.4.4 foo-4.example.com foo-4 In the Ideal condition you should met below condition: Your CDSW session should resolve the localhost as: !nslookup localhost Server: IP address
Address: IP address#53
Name: localhost
Address: 127.0.0.1
Name: localhost
Address: ::1 Your "/etc/hosts" file should be correct as per the Recommended Network names Configuration Your hdfs-site.xml should use FQDN or IP. NOTE: Having the short name entries of "namenode43,namenode57" in "/etc/hosts" file might work with your existing hdfs-site.xml but I would recommend to do that with FQDN way to avoid other issue. Please modify and let me know how this goes, I am waiting for this issue to be resolved 🙂🤞
... View more
