About yagoaparecidoti

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.

yagoaparecidoti · ‎04-28-2022

we need to block the DDL (create, drop, insert, update) for whoever is using IMPALA, is it possible to do this type of blocking? ps: user should only be able to SELECT with IMPALA and nothing else. DDL should only work via HIVE. Is it possible to do this type of blocking configuration?

yagoaparecidoti · ‎04-28-2022

hi@ChethanYM Thank you for the link. another question that popped up: we didn't find anything saying if the coordinators can be used in virtual machines, can you tell us if there is a problem?

yagoaparecidoti · ‎04-28-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-28-2022

hello @Elias / @GangWar , how are you? I ran ethtool on all hosts in the cloudera cluster and the network interface speed and duplex mode were returned successfully, this shows that ethtool is running smoothly. with ethtool working fine, what could be generating these alerts and leaving the agent not sending a heartbeat for a few seconds?

Online	Online
Last Visited	‎10-14-2025 07:59 AM

Member Since	‎02-28-2022 11:49 AM
Last Visited	‎10-14-2025 07:59 AM
Posts	171
Kudos received	14

Cloudera Community

Re: How to add Delay during Rolling Restart Until ...

Re: check date and time of access to some kudu tab...

Re: We need developer access to archive.cloudera.c...

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

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

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

block DDL in IMPALA, run only SELECT in IMPALA

Re: configure impala specialization with coordinat...

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

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