Summary : Rebalance option is greyed out in the Cloudera Manager under the HDFS -1 or Balancer Actions dropdown menu. Symptoms The Rebalance option is grayed out in the Cloudera Manager under the HDFS -1 or Balancer Actions menu. You have verified that they are no currently running Balancer operations under the HDFS-1->Balancer Instance->Commands tab. The HDFS Balancer menu option is normally greyed out if there is a active Balancer job running. Instructions To diagnose and workaround this issue, perform the following actions: Log into the Cloudera Manager SQL database and check the status of BALANCER in the Cloudera Manager database using the following command.  select CONFIGURED_STATUS, ROLE_TYPE FROM ROLES where ROLE_TYPE = "BALANCER" ;  The normal status is NA. If the status returned is BUSY then the status must be changed to NA using the following command.  update ROLES set CONFIGURED_STATUS="NA" where ROLE_TYPE = "BALANCER"; Re-execute the select statement to check to ensure the configured_status is now indicating the correct state. After changing the status the Rebalance option should no longer be greyed out in Cloudera Manager. ... View more

Hi @lukepoo . Yes, you can try to raise the timeouts as well do check if the regions of this table have a good locality. For the current run, it seems the timeout happened on the region ' 1e8adfc0af2cf791361126e24822e63c'. So you can check the region locality and try to compact them if its less than 1. ... View more

Hi @cdl-support . You can refer to the below article and check if those help.   https://my.cloudera.com/knowledge/Issue-with-Small-Files-in-HDFS?id=308948   Using Hive : https://docs.cloudera.com/best-practices/latest/impala-performance/topics/bp-impala-avoiding-small-files.html ... View more

hi @yagoaparecidoti Yes, the Block for the file would be present on the Datanode in either of the rack. So if you write a file with RF 3, 1 block will be present on a rack and its 2 replicas will be present on different Datanodes of 2nd rack. ... View more

HI @damon The most likely culprit, in this case, would be the Packet length crossing the jute buffer limit. As this is seen for the Kms service, verify if you are getting any warnings such as "Packet len is out of range!"   If you do, then raise the jute buffer for the Zookeeper service as well as for the Kms service ( client ) and restart the respective services to resolve this issue. ... View more