Member since
12-20-2022
84
Posts
19
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
204 | 05-08-2025 06:27 AM | |
256 | 04-02-2025 11:35 PM | |
252 | 03-23-2025 11:30 PM | |
244 | 03-06-2025 10:11 PM | |
683 | 10-29-2024 11:53 PM |
08-06-2024
11:17 PM
Apart from Zk ensemble, new broker details you need to have namespace updated for NN for RM nothing much will happen for Dev and Data engineer. Hive and Impala string will be changed. Tableau connection string with Hive will also change.
... View more
07-31-2024
01:15 AM
1 Kudo
Please check the permission for the nodemanager directory. The owner or group must be yarn. Then try to decommission and it will distribute the blocks to other datanodes and then will decommission.
... View more
07-31-2024
01:11 AM
1 Kudo
Please check if you have tgt created for all the Nodemanagers. It will fix the issue.
... View more
04-23-2024
06:18 AM
Hi @DanhH , Please accept this as a solution if it helped.
... View more
04-23-2024
06:18 AM
Hi @HadoopCommunity , If my solution. helped you Please accept it as a solution
... View more
04-22-2024
11:27 AM
Hi @yagoaparecidoti , You dont have to run the balancer. The blocks will recognize the racks and it will be done automatically.
... View more
04-22-2024
11:24 AM
Hi @JiHoone I think all your jobs that is running is allocated only the AM resources. Do one thing first set the "Configured Max AM limit" to 20%. Then set the Minimum user limit percent to 25% and run your jobs. Set user limit factor as 0.5.
... View more
04-22-2024
11:17 AM
Hi @ryu , yes you can search the details in the RM logs with the application Id. You will get the details of the resources asked by the application and resources provided by the RM
... View more
04-22-2024
11:10 AM
@ryu Please accept this as solution if your issue is resolved by the suggestion
... View more
04-22-2024
05:51 AM
@ryu 1.Check the queue that job is running in. See if that is allocated enough resources. 2.See if the queue is pending containers is showing or not. 3.If all these things are fine then start checking the locality if the job is running in node local or rack local. 4. Then go to node manager level and debug for local unix level slowness
... View more