It looks like you might have your resource management configured incorrectly for this query. The error message indicates that the query was not able to acquire sufficient resources to execute. In order to answer the question, you would need to provide more information on how your resource management is set up.
1> Do you have YARN integration turned on? If so how much of the server’s resource is available to HDB? 2> You did not provide sufficient information from the error log to see what is happening with resource management and what resources the query failed to get. 3> What to your resource pools look like? The default setup may not provide you what you are thinking your query is getting. 4> There is additional information in the HDB best practices on how to manage the number of query executors you query should receive. 5> What does the DDL look like that created the underlying table. What is the distribution on the underlying table? Is your table partitioned? 6> What does your cluster look like? Number of nodes, memory, cores, etc? The error message is not complaining about MadLib. It is complaining about resources. Fix the resource issue, and your query should run. James Campbell Data Engineer Pivotal Software P: 571-247-6511 E: jacampb...@pivotal.io On March 2, 2017 at 11:19:47 PM, Leonard Edwin (leonard.edw...@gmail.com) wrote: Hello, I have been evaluating your implementation of the HDB2.1.1 sandbox, as requested - to validate the MADLIB installation is working as stated in the 'Apache Madlib Confluence' tutorials. However, I get the following ERROR when trying to train the model, as specified in the tutorial: 18:30:25 [SELECT - 0 rows, 839.195 secs] [Code: 0, SQL State: XX000] ERROR: plpy.SPIError: failed to acquire resource from resource manager, queued resource request is timed out due to no resource (plpython.c:4663) Where: Traceback (most recent call last): PL/Python function "logregr_train", line 23, in <module> return logistic.logregr_train(**globals()) PL/Python function "logregr_train", line 133, in logregr_train PL/Python function "logregr_train", line 260, in __logregr_train_compute PL/Python function "logregr_train", line 75, in __compute_logregr PL/Python function "logregr_train", line 114, in __enter__ PL/Python function "logregr_train", line 197, in runSQL PL/Python function "logregr_train" ... 1 statement(s) executed, 0 rows affected, exec/fetch time: 839.195/0.000 sec [0 successful, 1 errors] QUESTION - what can I do to resolve the error and continue with my evaluation of MADLIB using HAWQ??
