Hi shelton, please write me the command that recovers snapshot data in such a way by retaining its ownership,timestamp,permissions and acls. Looking forward to hear from you. thanks ... View more

@Jay Kumar SenSharma I have selected option 3 (custom) . this path works for "Node1" and "Node2" . but in case of "Node3",it gives an error during the "Confirm Hosts" Step Thanks ... View more

@Jay Kumar SenSharmaThanks a lot! I got the desired output. but why it is showing "hdfs" the owner instead of "Mark" .although i change the ownership. Correct me where i was wrong : First of all i created user "Mark" [root@namenode] adduser Mark then check the space for user : [root@namenode] hadoop fs -ls /user My user not shown in the list so i create a space for my user [root@namenode] sudo -u hdfs hadoop fs - mkdir /user/Mark [root@namenode] hadoop fs -ls /user (now user show in the list) Change the ownership [root@namenode] sudo -u hdfs hadoop fs -chown Mark:hdfs /user/Mark Now i login to user hdfs [hdfs@namenode] hdfs dfs -mkdir /user/Mark/cards [hdfs@namenode] hdfs dfs -touchz /user/Mark/cards/largedeck.txt now login with "Mark" user and then type [Mark@namenode] hadoop fs -ls /user/Mark/cards Thanks ... View more

@Mudassar Hussain Ok good go ahead and do the setup and most probably we could do a remote session to check the ACL stuff. Please keep me posted. ... View more

Thanks a lot @Aditya Sirna ... View more

It is because the way how namenode works. It merges namespace repo (fsimage) periodically with edit logs file. To prevent namespace inconsistency it stops changing namespace by entering safemode. hdfs dfsadmin -safemode leave should work. ... View more

@Mudassar Hussain, Accepting the answer will do it. Thanks 🙂 ... View more

Thanks a lot @Jay SenSharma for your help. Today when i was login to my AWS machine. it does not start all service and give me an error 8080:Port and Ambari Server issue. I just Go inot @nameNode and write command : Service Iptables Stop and both issue solves 🙂 🙂 Hope it will work smoothly. Thanks again ... View more

Thanks @Jonathan Hurley got your point regarding raising question. My @Namenode was on Safemode that time when i was facing this alert. i put the @namenode into Normal mode. now the alert Purge. is this exactly the reason ? whats your views Thanks ... View more