Member since
07-30-2020
219
Posts
45
Kudos Received
60
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
435 | 11-20-2024 11:11 PM | |
490 | 09-26-2024 05:30 AM | |
1084 | 10-26-2023 08:08 AM | |
1852 | 09-13-2023 06:56 AM | |
2130 | 08-25-2023 06:04 AM |
11-07-2022
01:43 AM
Hi @lysConsulting The No route to host indicates that there is a network issue between this client and the HDFS cluster. I would suggest to check if the basic networking is working fine between these hosts.
... View more
11-07-2022
01:26 AM
Hello @Felix-Han Hope you are doing well. Since the Post by @rki_ referencing [1] for your team would fix the CQTBE for your team, We shall mark the Post as resolved. If your team have any further ask, Feel free to Update the Post likewise. Regards, Smarak [1] https://my.cloudera.com/knowledge/CallQueueTooBigException--Call-queue-is-full-on-000060020-too?id=73901
... View more
10-29-2022
12:04 AM
You can also try to split the table at the time of creation or split it now so that not all requests go to the same Region server which thereby creates a hotspot and might be a bottleneck.
... View more
10-28-2022
03:13 AM
1 Kudo
Hi @mazz , Check if the below article helps you in achieving this. You will need to modify the duration. https://community.cloudera.com/t5/Support-Questions/How-to-do-a-cleanup-of-hdfs-files-older-than-a-certain-date/m-p/182146
... View more
10-25-2022
10:31 PM
@hanumanth, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
10-20-2022
10:14 PM
@fengsh, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
10-10-2022
09:27 PM
Hello @cprakash Since we haven't heard from your Team, We are marking the Post as Resolved. Feel free to add your Team's observation whenever feasible. In Summary, Review the HMaster Logs to confirm the reasoning for ConnectionRefused. Few possible scenarios being Port 16000 is being used by any other Service Or, "master1" isn't correctly being mapped as per DNS Or, Port 16000 may be blocked. Regards, Smarak
... View more
09-25-2022
10:01 PM
@abdebja, have any of replies helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
09-19-2022
02:10 AM
Hi @Anlarin , It is always suggested to have a homogeneous disk storage across Datanodes. Within datanode, if there are heterogeneous volumes, then when the block replicas are written to new disks on a Round Robin fashion, the disks with less capacity will fill up faster compared to the disks with higher size. If the client is local to Node 2, then it will place the 1st block on that node and it's expected to fill faster. By choosing "Available Space Policy" the DNs would take into account how much space is available on each volume/disks when deciding where to place a new replica. To achieve writes that are evenly distribution in percentage of capacity on drives, change the choosing policy (dfs.datanode.fsdataset.volume.choosing.policy)to Available Space. If using Cloudera Manager: Navigate to HDFS > Configuration > DataNode Change DataNode Volume Choosing Policy from Round Robin to Available Space Click Save Changes Restart the DataNodes The above property only helps for volumes within Datanode. https://docs.cloudera.com/documentation/enterprise/latest/topics/admin_dn_storage_balancing.html - Was your question answered? Please take some time to click on “Accept as Solution” below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more