Hi  @skommineni We don't support  setting Ozone as the default fs yet (Not fully integrated). This will be supported in future release. As a workaround you can try configuring HA (Active + Standby NN) instead of secondary NN and then set ozone as default fs.  ... View more

HDFS has a trash facility, in which deleted files are not actually deleted but rather are moved to a trash folder, where they remain for a minimum period before being permanently deleted by the system. The minimum period in minutes that a file will remain in the trash is set using the fs.trash.interval configuration property in core-site.xml.   The above said is true only when we have trash enabled or when -skipTrash is not used during delete operation. So please check whether the directory is present under "/user/<user-name>/.Trash". If the file is present then we can simply use mv or ditscp to recover the file to its original location.   If you have executed the operation recently then you can check NN UI for Blocks Pending Deletion. If this shows 0 blocks/relicas, then this means the blocks are already removed, and then we might need to use other mechanisms like snapshot or copy from the remote cluster. Please refer to below article for more details. https://community.cloudera.com/t5/Internal/How-to-Recover-Files-in-HDFS-After-Removing-or-Deleting/ta-p/73885 ... View more

Hello @pauljoshiva The NameNode endeavors to ensure that each block always has the intended number of replicas. The NameNode detects that a block has become under- or over-replicated when a block report from a DataNode arrives. When a block becomes over replicated, the NameNode chooses a replica to remove. The NameNode will prefer not to reduce the number of racks that host replicas, and secondly prefer to remove a replica from the DataNode with the least amount of available disk space. The goal is to balance storage utilization across DataNodes without reducing the block's availability.   Hope this answers your query.      Regards, Manoj ... View more

Yes, right. Please move all the contents and start RMAN service once again.  ... View more

How much data did you delete ? Did checkpoint happen after you deleted data ? Also please check if any snapshots are present ?  HDFS CLI "du" output not only include normal files but also includes the files that have been deleted and exist in snapshots (which is true in terms of real resource consumption).   Please check the output using -x flag which excludes snapshot from calculation.   hdfs dfs -du -x -s -h /path     ... View more