Hello, sorry but due to the urgency I abandoned the migration of the components and finally reinstalled everything. I now have a hbase table export problem and submitted a new topic. If anyone here would take the time to help me find a solution, that would be very kind. ... View more

@Shelton  I could not start namenode with ambari ui when setting safemode to off mode. Please could you helpme out! And also while setting safemode to 'ON'  does not allow me to do task. ... View more

Hello @hebamahmoud  If the issue is has been from any of the above responses, Could you accept it as a solution? Regards, Chethan YM ... View more

@Shelton, wow apologies, now I´m reading, excellent test. Could you do testing  with TLS/SSL? I still haven`t solved this..  😞   Thank you for your support. ... View more

@Shelton Please note that the directory on edge server to which I am trying to copy the file is already present. So ideally it should not try to perform mkdir operation. as I mentioned in my first post, it is looking for the directory in cwd of the node where the code is being executed and since it is not able to find it , it is trying to create one. So basically it should look for the directory in edge server instead of the directory mentioned in the cwd of the error posted. ... View more

@YasBHK  File /user/hdfs/data/file.xlsx could only be written to 0 of the 1 minReplication nodes. There are 1 datanode(s) running and 1 node(s) are excluded in this operation. So that means your data node is down can you restart the HDFS service and retry? ... View more

@BrianChan  You will need to manually perform the checkpoint on the faulty node. If the standby NameNode is faulty for a long time, generated edit log will accumulate. In this case, this will cause the HDFS or active NN to take a long time to restart and could even fail to restart because if the HDFS or active NameNode is restarted, the active NameNode reads a large amount of unmerged editlog. Is your NN setup active/standby? Fr the below steps you could as well use CM UI to perfom the tasks Quickest solution 1 I have had occasions when a simple rolling restart of the Zk's would resolve that biut I see the checkpoint lag goes to > 2 days Solution 2 Check the most up to date on both NN by comparing the dates of files in the directory. $ ls -lrt /dfs/nn/current/ On the Active NN with the latest editlogs as hdfs user $ hdfs dfsadmin -safemode enter $ hdfs dfsadmin -saveNamespace Check whether the latest generated fsimage timestamp is the current time. If yes, the combination is executed correctly and is complete. $ hdfs dfsadmin -safemode leave Before restarting the HDFS or active NameNode, perform a checkpoint manually to merge the metadata of the active NameNode. The restart the standby the newly generated files should now automatically be shipped and synced this could take a while < 5 minutes and your NN should all be green ... View more

@ambari275  These are the steps to follow  assuming you are logged in as root # su - hdfs   $ klist -kt /etc/security/keytabs/hdfs-headless.keytab   Then the output should give you the principal to use $ kinit -kt /etc/security/keytabs/hdfs-headless.keytab     ... View more