About ChethanYM

ChethanYM · ‎11-10-2021

Hi @drgenious , 1. can you attach the full query profile of it to take a look? 2. You mean query is finished in 8 minutes but why Unregister query has took 19 min am i correct ? if not please elaborate the issue. 3. How you are running the queries from impala-shell or Hue? 4. what is the session timeouts you have in the cluster for impala queries? Regards, Chethan YM

ChethanYM · ‎11-10-2021

Hello @raghu9raghavend , Please provide the error/stack-trace for the failure. Regards, Chethan YM

ChethanYM · ‎11-04-2021

Hi, As per my previous comment can you destroy it and restart the LLAP and see if this works. Note: llap0 is the default application that will be running if LLAP is installed it will be recreated even if you destroy it and restart the service. #yarn app -destroy llap0 Regards, Chethan YM

ChethanYM · ‎11-04-2021

Hi, Can you perform these steps and see if this helps to restart LLAP. 1. Check ps -ef | grep -I llapdaemon run it on the node managers and kill the process if queue utilisation was full. check in all the nodemanager ,if any stale llap daemon process is running > ps -ef | grep llap 2. su - hive # yarn app -status llap0 # yarn app -destroy llap0 Regards, Chethan YM

ChethanYM · ‎11-04-2021

Hello @ighack , You are welcome..!! Was your question answered? Please Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. Regards, Chethan YM

ChethanYM · ‎11-02-2021

Hi @ighack , As like yarn, there is no direct options for impala admission control pool, As per the cloudera documentation you need to select "default settings" under impala admission control to add users and group. Below is the screenshot of it. After you click on Default Settings you need to choose "Allow these users and groups to submit to this pool" to add users and groups. Regards, Chethan YM

ChethanYM · ‎11-01-2021

Hi @harnu , Could you add these below values to /etc/security/limits.conf file and see if this helpfull? If you already have these values try to increase it and rerun the query. hive soft nofile 65000 hive hard nofile 65000 hive soft proc 80000 hive hard proc 80000 Update limits.conf with above settings and restart hiveserver2 service while stopping all the services on that node. Please su - hive and then ulimit -a to check whether the parameters are updated for no of open files and max user process. Regards, Chethan YM Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.

ChethanYM · ‎11-01-2021

Hi @wert_1311 , Seems to be "load_catalog_in_background" option is set to true in your cluster, This can result in lock contention. The recommended value for this parameter is false. Please change the value to False and see if this helpful. And if you are also seeing any JVM pauses in the catalog logs try to increase the catalog heap size and monitor the cluster. https://docs.cloudera.com/documentation/enterprise/5-16-x/topics/impala_config_options.html Regards, Chethan YM Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.

ChethanYM · ‎11-01-2021

Hi @ighack , When click on Submission Access Control tab to specify which users and groups can submit queries by default, anyone can submit queries. To restrict this permission, select the Allow these users and groups option and provide a comma-delimited list of users and groups in the Users and Groups fields respectively. I am attaching the screenshot for your reference. Please check the below Cloudera documentation for the same. https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/impala_howto_rm.html#enable_admission_control__d3424603e189 Regards, Chethan YM Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.

ChethanYM · ‎10-25-2021

Hi @pauljoshiva , Sqoop uses local hive which does automatic connect so you would need to modify the information in beeline-site.xml as referenced in below article: https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-Usingbeeline-site.xmltoautomaticallyconnecttoHiveServer2 Hence please go to /usr/hdp/<VERSION>/hive/conf then open the beeline-site.xml and modify there. Regards, Chethan YM

Online	Offline
Last Visited	‎08-28-2025 09:14 PM

Member Since	‎03-06-2020 05:48 AM
Last Visited	‎08-28-2025 09:14 PM
Posts	406
Kudos received	55

Cloudera Community

Re: impala forces full table scan

Re: Sqoop export fails from hive to oracle when co...

Re: Multi Node Hadoop Cluster setup with Hbase and...

Re: Hive connecting to node that does not exist

Re: Error creating login context using ticket cach...

Re: Query seems executing despite it is finished

Re: msck repair is failing for random partitions

Re: HiveServer2 Interactive Start Failed on HDP3

Re: HiveServer2 Interactive Start Failed on HDP3

Re: How can I edit Submission Access Control of Im...

Re: How can I edit Submission Access Control of Im...

Re: Error: Error while processing statement: FAILE...

Re: Impala Error updating the catalog due to lock ...

Re: How can I edit Submission Access Control of Im...

Re: How do you pass on Hiveserver2 URL in Sqoop co...