Hello @rajatsachan, Using the Delete Policy, you may set up any of the below options Delete Policy - Whether files that were deleted on the source should also be deleted from the destination directory. This policy also determines the handling of files in the destination location that are unrelated to the source. Options include: Keep Deleted Files - Retains the destination files even when they no longer exist at the source. (This is the default.). Delete to Trash - If the HDFS trash is enabled, files are moved to the trash folder. (Not supported when replicating to Amazon S3.) Delete Permanently - Uses the least amount of space; use with caution.   Review the replication document for more details: https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_bdr_hdfs_replication.html   Cheers! ... View more

Hello @HareeKrushnan    I see that you are using a custom script to retrieve keytabs from the local filesystem. The script is failing as it is unable to find the required keytabs at the location cp: cannot stat ‘/etc/hadoop/conf/keytabs/spark_clouderadp02.ibm.cloud@IBM.CLOUD.keytab’: No such file or directory>>   Please note that to use the custom script the KDC administrators should create the required principals and keytabs, and store them securely on the Cloudera Manager Server host.   Please review the below document for more information on using a Custom Kerberos Keytab Retrieval Script https://docs.cloudera.com/documentation/enterprise/5-16-x/topics/sg_keytab_retrieval_script.html   Let us know if this helps.   Cheers! Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

@Deaks @HGeorge    This issue can occur if you had some previous mount points and later if you have unmounted them. In some unusual scenarios, CM agent will still tries to grab the filesystem information of that mount point and fails.   To temporarily suppress this error, update the /etc/cloudera-scm-agent/config.ini on each of the hosts affected to: 1. In the line that lists the nodev filesystems: # The list of non-device (nodev) filesystem types which will be monitored. monitored_nodev_filesystem_types=nfs,nfs4,tmpfs   2. Please change the uncommented line to read as : monitored_nodev_filesystem_types=nfs,nfs4   3. Restart the cloudera manager agent with: service cloudera-scm-agent restart   Br, Tarun Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more