About yagoaparecidoti

yagoaparecidoti · ‎05-25-2022

hi @rblough 1) - answer: Masters | 3 Tablet Servers | 5 Tables | 48 Tablets | 481 Replicas | 1443 2) - answer: According to the chart "Total Tablet Size On Disk Across Kudu Replicas", it has more than 710GB 3) - answer: exist 5 4) - answer: exist 3 threads 5) - answer: memory_limit_hard_bytes = 60GB block_cache_capacity_mb = 15GB

yagoaparecidoti · ‎05-25-2022

kudu service has 3 kudu master and 5 kudu tablet among these 5 kudu tablet, 3 of them have high memory usage, 60GB has been set for each kudu tablet and it is using more than 85% to 90% of that memory and with that it ends up causing jobs failure below shows the memory usage behavior: TABLET SERVER: hostname04.local - USE MEMORY: 55.28G / %: 92.13% TABLET SERVER: hostname05.local - USE MEMORY: 54.22G / %: 90.38% TABLET SERVER: hostname06.local - USE MEMORY: 29.05G / %: 48.42% TABLET SERVER: hostname07.local - USE MEMORY: 28.47G / %: 47.46% TABLET SERVER: hostname08.local - USE MEMORY: 54.99G / %: 91.66% memory usage graph of all kudu tablet in cloudera manager: would like to understand why kudu is having this behavior and how can we reduce this memory usage? PS: kudu service is installed and being managed by cloudera manager express in version 5.16.2 and kudu service is in version 1.7

yagoaparecidoti · ‎05-24-2022

thank you @ask_bill_brooks I had seen this thread you passed, but it doesn't explicitly say which version of CM/CDH to run github's log4j script procedure. but I will consider version 5.x and 6.x to run this script.

yagoaparecidoti · ‎05-24-2022

Hello about log4j2 failure (CVE-2021-44228) in cloudera there is the KB: https://my.cloudera.com/knowledge/Resolution-for-TSB-2021-545---Critical-vulnerability-in-log4j2?id=332012 instructs to run the script to remove a class in the jar etc. our doubt is, do we need to run this script in any version of CM / CDH or just the version from 6.x.x?

yagoaparecidoti · ‎05-20-2022

LB AWS sticky sessions settings is for LB HTTP/HTTPS only in this case the LB we are using is TCP on ports 21000 and 21050 the session timeout you say in the impala service, right? would be the "idle_query_timeout" and "idle_session_timeout" options, right?

yagoaparecidoti · ‎05-20-2022

hi @aakulov the cluster is on AWS and the AWS LB is being used on ports 21050 of the impala daemon, in which case this LB may be having this problem? sould it be that in this LB we can also change it to "source"?

yagoaparecidoti · ‎05-19-2022

queries in hue using impala are returning the following error: "results have expired, rerun the query if needed" as shown in the screenshot below: what could be causing this error and how to fix this issue?

yagoaparecidoti · ‎05-17-2022

When we restart or start kudu tablet server component through cloudera manager, it takes a long time to communicate with kudu master, it takes more than 10 minutes. why does this occur? when we start the kudu tablet server component and follow the log, it keeps loading the lines as shown in the screenshot below:

yagoaparecidoti · ‎05-03-2022

hi @GangWar , I followed the behavior of the host and when the error appeared in the cloudera manager I ran ethtool and it returned the information without any problem.

yagoaparecidoti · ‎04-29-2022

hi @ChethanYM unfortunately we need to do this type of blocking only in IMPALA, in HIVE it has to work normally. when blocking by sentry, it will be replicated for any type of access that the user will use, such as hive, impala, beeline, etc.

Online	Online
Last Visited	‎12-12-2024 09:52 AM

Member Since	‎02-28-2022 11:49 AM
Last Visited	‎12-12-2024 09:52 AM
Posts	144
Kudos received	13

Cloudera Community

Re: how to create a flow in nifi that reads a hive...

Re: how create, export and import full nifi templa...

Re: [Cloudera][ImpalaJDBCDriver](500593) Communica...

Re: deploy rack concept in cluster

Re: yarn run logs - error getting logs at hostname...

Re: kudu service is having high memory usage on sp...

kudu service is having high memory usage on specif...

Re: log4j2 failure (CVE-2021-44228) in cloudera

log4j2 failure (CVE-2021-44228) in cloudera

Re: ERROR- HUE - Results have expired, rerun the q...

Re: ERROR- HUE - Results have expired, rerun the q...

ERROR- HUE - Results have expired, rerun the query...

kudu tablet server slow to start

Re: URGENT - Constant "Network Interface Speed Unk...

Re: block DDL in IMPALA, run only SELECT in IMPALA