hawq-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Campbell <jacampb...@pivotal.io>
Subject Re: Could not allocate enough memory
Date Fri, 13 Jan 2017 18:09:27 GMT
There are several things that could cause this error.  Can you answer the
following questions:

1>  Are you using YARN integration?
2>  Provide a copy of your log file where the query was running.  Sometimes
the you error you describe can be related to RM configuration
3>  Provide a snipped of the DDL used to create the table.  You don’t have
to provide every column name if the table has a lot of columns.
4>  What parameters did you set at the server level if different from
default?  Particularly pertaining to resource management.  If using YARN,
how are your resource queues setup?
5>  Can you provide at least an explain plan if not an explain analyze

That should help for starts.  I have seen a similar error message before.

James Campbell
Data Eningeer
Pivotal Software
P:  571-247-6511
E:  jacampbell@pivotal.io

On January 13, 2017 at 1:00:25 PM, Dmitry Buzolin (dmitry.buzolin@theice.com)

I am trying to run TPC-DS with has distributed tables and run into this

master/04_load/051.insert.call_center.sql:1: ERROR:  Could not allocate
enough memory! bucket number of result hash table and external table should
match each other (cdbdatalocality.c:4245)

I have verified my memory and O/S  kernel configuration is correct. Is
there a problem between external and hash table definition mismatch in
terms on number of buckets? What else I can check?



This message may contain confidential information and is intended for
specific recipients unless explicitly noted otherwise. If you have reason
to believe you are not an intended recipient of this message, please delete
it and notify the sender. This message may not represent the opinion of
Intercontinental Exchange, Inc. (ICE), its subsidiaries or affiliates, and
does not constitute a contract or guarantee. Unencrypted electronic mail is
not secure and the recipient of this message is expected to provide
safeguards from viruses and pursue alternate means of communication where
privacy or a binding message is desired.

View raw message