Thanks @Harsh J, Appreciate your help. Just as a feedback on part of Cloudera Documentation should also include an example with Sqoop1 and Sqoop2 and that would have been very helpful too for all the users who deploy Sqoop. ... View more

I have installed Sqoop 1 Client as per your given document but I have an issue and Sqoop 1 client is not starting. I have raised a separate post for it. Can you please look into it as well and help. http://community.cloudera.com/t5/Data-Ingestion-Integration/Sqoop-1-Client-not-started/m-p/41188 ... View more

Yes the link was helpful.  As per the property "dfs.datanode.du.reserved", it was configured to use 4.25 GB and hence I consider now that 4.25 GB is allocated for each data directory in a given node. Since I had two data directory partitions, the reserved space combined would be 8.5 GB per node and which brings the configured capacity on each node to be 23.5 GB (32GB - 8.5GB). I arrived at the following formula === > Configured Capacity = Total Disk Space allocated for Data Directories (dfs.data.dir) - Reserved Space for Non DFS Use (dfs.datanode.du.reserved)  ... View more

@ Benjamin Leonhardi Why sorting is written before shuffling? I think sorting always happen after the shuffling. As there is already combiner to combine(sort) the output on single node. I think when all intermediated data collected using shuffling then sorting is use to make one single input file, which will use by reducer. ... View more

Thanks Neeraj ... View more

Hi Chris, my cluster was hacked and the HDFS data was deleted (includ /user/ and the trash files). I can see in /hadoop/hdfs/namenode the fsimage_ file before the deletes were applied. Could you explain how I would go about reverting to the older fsimage_ file? ... View more

@Chris Nauroth Thanks for sharing your opinion on it. I do respect it 🙂 I was just curious to know more context behind your inputs. Appreciate it!!! ... View more

Ah that's a good catch. Thanks Joseph ... View more

In more elaboration, any namespace changes on Active node is recorded by JNs and Standby node reads these edits from these JNs. And Standby node applies them to own namespace and try to be as close to Active node as possible. In failover scenario, SB node reads all edits from JNs before promoting it-self to Active so that there is full-sync before failover occurs.   Hope further details help with better understanding. ... View more