@scottwong,    The thread you've posted your question to was marked 'Solved' quite a while ago and hasn't had any activity recently. You would have a better chance of receiving a satisfactory resolution by posting a new question. This will also provide the opportunity to provide details specific to what you are attempting to do that could aid other community members in providing a more tailored answer to your issue.      ... View more

This enables the diskbalancer feature on a cluster. By default, disk balancer is disabled. then why is your config  + <value>false</value>   ... View more

@DanielWhite   I had the similar issue long back and below was my findings   Please check the owner of HDFS folder/files for the corresponding db that you are trying to delete. if you are the owner and trying to delete the table/db from hive/impala, it will delete both metadata and hdfs file/folder. Whereas you are not the owner of hdfs folder/file but got an access in hive/impala to manage data and trying to delete it, it will just delete the metadata but not the underlined folder/files from hdfs   pls try this with a sample db/table for more understanding ... View more

@DanielWhite,   Can you clarify what you mean by "source server?" Really, the answer is No.   Your source configuration dictates what NameNode(s) to communicate with. Your source's NameNodes tell clients where to get blocks. Those blocks can be on any DataNode in the source cluster.   On the target side where the MapReduce Job runs, the Resource Manager decides on which nodes the Mappers will run. ... View more

@DanielWhite,   There is a Cloudera Manager command and a YARN job. - To Abort the command, you can click on the Command Details button under the replication schedule with a running command. - If the YARN job continues to run, you can kill it like any other YARN job.   Aborting/Killing is safe.  The next time you run replication, any files that were already copied will be skipped; any that weren't copied will be copied.     ... View more