About AcharkiMed

AcharkiMed · ‎08-08-2019

Hi @Zane- This is an OOM (Out If Memory) error, it simply means that this query needs more memory to be completed; it usually occurs when the cluster is in charge. The request has exceeded the existing memory. The solution is to add more memory to your nodes or to add more nodes. Otherwise, try to optimize your queries, and you can make sure that your impala setting is optimal too. https://www.cloudera.com/documentation/enterprise/latest/topics/impala_performance.html Good Luck.

AcharkiMed · ‎07-04-2019

Have you made any manual changes to the metastore user or database permissions? because it looks like the DBS table is not found in metastore DB! Remark: check if the CM point to the correct metastore DB with the pertinent user.

AcharkiMed · ‎07-04-2019

Hi @andreas It looks like you have a connectivity issue with hive metastore.. try to put off the firewall and test. Else, please share with us those log files: /var/log/hive/hadoop-cmf-hive-HIVEMETASTORE-XXXX.log.out /var/log/impalad/impalad.hdm1.emd.impala.log.INFO.YYYYYYY Good luck

AcharkiMed · ‎07-03-2019

HI @punshi Do you use the QuickStart VM for CDH 5.13? Indeed, the VM is just for testing !! To unlock the real power of the impala (CDH), you should have a cluster so that you can benefit from the senergy of several nodes. Anyway, you can improve your query time by: 1- Set PARQUET_FILE_SIZE = 256MB instead of 512MB. 2- Try to minimize the number of partitions (in fact, I think in your case, the year is sufficient). NB: I think that in a cluster that has more than 10 nodes, this request will not exceed 2 to 4 seconds. Good luck.

AcharkiMed · ‎05-06-2019

Hi @anis447 Can you bring us this queries results in SQL server and Impala: Select avg(tagno) from tag; Select avg(tagno) from has_tag; Select count(*) from tag where tagno is null; Select count(*) from has_tag where tagno is null; Also try to add this on Impala query, and let us know if there is any change: ... Inner join has_tags hit on (s.tagno = hit.tagno and s.categorycode = hit.categorycode) ... Good luck.

AcharkiMed · ‎04-28-2019

Hi @bridgor It looks like you have a firewall issue between your nodes.. try to check iptables. Please share with us the impalad log files. Good luck.

AcharkiMed · ‎04-22-2019

Hi, the unix_timestamp function return a number of seconds but it seems that ipid.bk_eff_strt_dt column is inserted with the milliseconds number!? About your query try this: SELECT COUNT(*) FROM ipid WHERE unix_timestamp('20190124',"yyyyMMdd")*1000 BETWEEN ipid.BK_EFF_STRT_DT AND ipid.BK_EFF_END_DT; Good luck.

AcharkiMed · ‎02-09-2019

Hi @Tim Armstrong While IMPALA-1618 steel open and unresolved, I confirmed that this "workaround" is safe and efficient (I'm using it on a large scope and during more than 9 months) so that this is the only solution I find to solve or -get around- this big problem. Hope that the main problem will be fixed ASAP. Thanks for the remark.

AcharkiMed · ‎02-09-2019

Hi @Bishnup If you still have the same problem please try to share with us your URL string.

AcharkiMed · ‎01-30-2019

Hi @Rr, Please give us more details, errors messages or screenshots so we can help you.

Online	Offline
Last Visited	‎05-25-2022 11:41 AM

Member Since	‎07-17-2017 07:15 AM
Last Visited	‎05-25-2022 11:41 AM
Posts	143
Kudos received	16

Cloudera Community

Cloudera Community

Re: What performance to expect from Cloudera VM ?

Re: Impala date

Re: Error 1107

Re: Cannot connect to Impala via ODBC

Re: Getting improper "Unexpected character" using ...

Re: ExecQueryFInstances rpc query_id=e74ef8d9b9215...

Re: Error starting Impala

Re: Error starting Impala

Re: What performance to expect from Cloudera VM ?

Re: Same query, same data, different results betwe...

Re: Impala daemons constantly connecting/disconnec...

Re: Impala date

Re: Impala ODBC/JDBC bad performance - rows fetch ...

Re: Impala ODBC/JDBC bad performance - rows fetch ...

Re: Error 1107