About urbanlad20

urbanlad20 · ‎07-19-2019

There is nothing shown in the Error status file and its kind of a dead end. Also, KMS has been enabled in the Source cluster. Tried manually doing a DistCp -update which was not working initially, but after removing the HDFS user from the blacklist in the kms-acls.xml file, it worked out fine. Attached is the snap of the Error-status.csv file

urbanlad20 · ‎07-15-2019

1. Nope. Setting it up for the first time. Both the clusters are SSL enabled using self-signed certs. Peering has been done successfully. 2. Yes 3. Nope. Using the replication schedules under the Backup tab.

urbanlad20 · ‎07-15-2019

The HDFS replication is failing even after the successful completion of the MapReduce job with the following error: ERROR distcp.DistCp: Job failed to copy 709 files/dirs. Please check Copy Status.csv file or Error Status.csv file for error messages INFO distcp.DistCp: Used diff: false INFO distcp.DistCp: Distcp failed to copy some files/dirs, skipping delete and rename snapshot operations on Source INFO distcp.DistCp: Distcp failed to copy some files/dirs, skipping delete and rename snapshot operations on Target The cluster is running with CDH 5.15.1. There are enough resources available in the destination cluster for the running of MapReduce job for DistCp. This is critical. Please assist.

urbanlad20 · ‎06-21-2019

I've already tried deleting spark, then restarted the namenode, but it didn't help. Namenode is still looking for that file. Again I installed spark and restarted the namenode, still no luck

urbanlad20 · ‎06-15-2019

Facing this issue with the namenode down. It is a parcel based CDH 5.15.2 installation on AWS. 9:15:18.262 PM ERROR NameNode Failed to start namenode. java.io.FileNotFoundException: File does not exist: /user/spark/spark2ApplicationHistory/.5e9b4c52-032a-4469-b278-80aa6254cfdf at org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:66) at org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:56) at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.applyEditLogOp(FSEditLogLoader.java:429) at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:232) at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:141) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadEdits(FSImage.java:903) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:756) at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:324) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1152) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:799) at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:614) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:676) at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:844) at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:823) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1547) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1615) 9:15:18.264 PM INFO ExitUtil Exiting with status 1 9:15:18.265 PM INFO NameNode SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down NameNode at xxxx.xxxx.xxxx/**.**.**.** ************************************************************/ Stuck from two days. Any help will be highly appreciated. Cheers,

Online	Offline
Last Visited	‎07-22-2021 06:21 PM

Member Since	‎05-27-2019 09:54 PM
Last Visited	‎07-22-2021 06:21 PM
Posts	8

Cloudera Community

Re: HDFS replication failing in BDR

Re: HDFS replication failing in BDR

HDFS replication failing in BDR

Re: Failed to start namenode. java.io.FileNotFound...

Failed to start namenode. java.io.FileNotFoundExce...