@Maeve Ryan You can decrease space for non-HDFS use by setting dfs.datanode.du.reserved to a low value. It's set per disk volume. You can also freed it up by deleting any unwanted files from the datanode machine such as hadoop logs, any non hadoop related files (other information on the disk), etc. It cannot be done by using any hadoop commands. ... View more

Did you tried restarting secondary namnode? if not then first we would try to do restart. ... View more

@Adi Jabkowsky Since you added new high capacity nodes into the cluster therefore first it would be recommended to run HDFS balance multiple times specially when your cluster is less load or any idle window(for best output) and we should start balancer threshold value from a high number to lower value, Example start with 10 and end with 5. Though it is not guaranteed that you will get fully balanced cluster as per threshold in single shot but balancer will try it best during multiple runs. I think it tries to balance 10G of data at once. Also namenode has limits on how many blocks can be moved at one time, In addition to that you may also consider increasing below properties values to optimize balancer. dfs.datanode.max.xcievers / dfs.datanode.max.transfer.threads dfs.datanode.balance.max.concurrent.moves dfs.datanode.balance.bandwidthPerSec ... View more

can you please check the RM logs for any possible errors? ... View more

Can you please provide logs or error messages which you are getting? Also did you tried using below parameters on hive shell? set hive.execution.engine=spark; set spark.master=yarn-client; set spark.eventLog.enabled=true; set spark.executor.memory=512m; set spark.executor.cores=2; ... View more

Thanks for sharing the root cause 🙂 ... View more

Can you please share the query and tables DDL? ... View more

@mike pal Thanks Mike for confirming, would be great if you can click on best answer 🙂 ... View more