Member since
07-30-2020
216
Posts
40
Kudos Received
59
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
276 | 09-26-2024 05:30 AM | |
988 | 10-26-2023 08:08 AM | |
1745 | 09-13-2023 06:56 AM | |
1975 | 08-25-2023 06:04 AM | |
1448 | 08-17-2023 12:51 AM |
08-25-2023
06:04 AM
Generally, the size of data blocks would be 128mb across all the Datanodes. But, if you have small files then you might see smaller blocks on some Datanodes as well. So Datanodes with different disk spaces would have uneven "Number of Blocks" and the Balancing happens based on the difference in the DFS usage and not by the difference in block count.
... View more
08-24-2023
04:57 AM
Did you make any changes at the KDC end prior to seeing this issue? Are there any other services hosted on this node that are working fine?
... View more
08-24-2023
03:33 AM
@Crash you can set up load balance at a disk level for the Datanodes. Refer : https://docs.cloudera.com/documentation/enterprise/5-16-x/topics/admin_dn_storage_balancing.html
... View more
08-17-2023
12:51 AM
Hi @Ben1996, As this is very specific use case, I don't see any Cloudera doc which could cover this. The basic requirements would be to import the hdfs module and provide the HDFS configs. For ex, https://tahiriamine9.medium.com/python-hdfs-cd822199799e#:~:text=Let's%20have%20an%20example%20of,into%20HDFS%20with%20CSV%20format.
... View more
08-07-2023
05:42 AM
I would suggest keeping one jar file at a time and checking. 1) /home/hadoop/hbase/hbase-2.5.5/lib/hbase-shaded-netty-4.1.4.jar!/META-INF/native/liborg_apache_hbase_thirdparty_netty_transport_native_epoll_x86_64.so 2) /home/hadoop/hbase/hbase-2.5.5/lib/phoenix-client-hbase-2.5-5.1.3.jar!/META-INF/native/liborg_apache_hbase_thirdparty_netty_transport_native_epoll_x86_64.so
... View more
08-04-2023
12:38 AM
1 Kudo
https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/phoenix_installation.html#concept_ysq_t4n_c3b
... View more
08-04-2023
12:36 AM
@Noel_0317 Do you have rack awareness configured for the Datanodes? Also, check for any disk-level issues on the datanode. Try enabling Debug for block placement : log4j.logger.org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy=DEBUG
log4j.logger.org.apache.hadoop.hdfs.protocol.BlockStoragePolicy=DEBUG
... View more
07-30-2023
10:00 AM
1 Kudo
It requires Hbase cluster as its a SQL layer on top of Hbase
... View more
07-28-2023
10:09 AM
1 Kudo
@sra_vis For CDP, In Cloudera Manager, click Home Click to the right of the cluster name and select Add Service. A list of service types display. Select Phoenix from the list and click Continue. Follow the wizard to add the Phoenix service. For HDP : https://docs.cloudera.com/HDPDocuments/HDP2/HDP-2.6.1/bk_command-line-installation/content/ch_install_phoenix_chapter.html
... View more
07-28-2023
09:57 AM
1 Kudo
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