Hi,
What should I be doing if I get the following error in vertica 5 ?
Error Details: com.vertica.util.PSQLException:ERROR: Insufficient resources to execute plan on pool general [Timedout waiting for resource request: Request exceeds limits: Memory(KB) Exceeded: Requested = 7780003, Free = 3990255 (Limit = 11436290, Used = 7446035)]
Thanks
Brendon
Insufficient resources to execute plan on pool general erro
Moderator: NorbertKrupa
-
- Newbie
- Posts: 17
- Joined: Wed Sep 12, 2012 8:28 pm
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: Insufficient resources to execute plan on pool general e
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Re: Insufficient resources to execute plan on pool general e
The referred to topic is focussed mostly on MEMORYCAP. This error is a timeout - where the resources couldn't be allocated before the resource timeout was hit. The tip there on delete vectors could be applicable here - you'll have to assess that (check the delete_vectors table).
In the vertica.log for the initiator node for the query that failed, you'll find a reference to the node that failed to get resources. Go to the vertica.log for that node, and you'll find some output dumped to the log that shows what was executing when the timeout occurred, how much memory each query was using, and the queries that were queued. This will allow you to see if one query was taking the memory, or a number of queries, and to assess how long the offending queries were running for. If it's a single query taking a lot of memory, then it's probably a join with a large inner relation or a cross join. The resolution will depend on what you see for the queries and their explain plans.
In the vertica.log for the initiator node for the query that failed, you'll find a reference to the node that failed to get resources. Go to the vertica.log for that node, and you'll find some output dumped to the log that shows what was executing when the timeout occurred, how much memory each query was using, and the queries that were queued. This will allow you to see if one query was taking the memory, or a number of queries, and to assess how long the offending queries were running for. If it's a single query taking a lot of memory, then it's probably a join with a large inner relation or a cross join. The resolution will depend on what you see for the queries and their explain plans.
Sharon Cutter
Vertica Consultant, Zazz Technologies LLC
Vertica Consultant, Zazz Technologies LLC
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: Insufficient resources to execute plan on pool general e
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Re: Insufficient resources to execute plan on pool general e
Yes - I like that discussion
Sharon Cutter
Vertica Consultant, Zazz Technologies LLC
Vertica Consultant, Zazz Technologies LLC