Hi,
I'm keep getting the following errors while running the database designer, and it's getting hung in half way through.
Can you please help me understand this error.
Insufficient resources to execute plan on pool dbd [Timedout waiting for resource request: Due to queued higher priority queries, general cannot supply required overflow resourcesQueries Exceeded: Requested = 1, Free = 0 (Limit = 9997, Used = 9997); Threads Exceeded: Requested = 4, Free = 0 (Limit = 21494, Used = 21494); File Handles Exceeded: Requested = 4, Free = 0 (Limit = 50831, Used = 50831); Memory(KB) Exceeded: Requested = 15247, Free = 0 (Limit = 2376892, Used = 2376892)]
Thanks in advance
Shaz
Errors while running DBD
Moderator: NorbertKrupa
Re: Errors while running DBD
Hi!
[DELETED]
[DELETED]
Last edited by id10t on Fri May 08, 2015 4:47 pm, edited 1 time in total.
Re: Errors while running DBD
I'm using version 6. Could you please provide more details/commands how to modify all these "fail" parameters?
Re: Errors while running DBD
Hi,
Awaiting for your reply. I need more details on where all "fail" parameters need to be modified. Is it something on OS or within Vertica DB.
Thanks,
Awaiting for your reply. I need more details on where all "fail" parameters need to be modified. Is it something on OS or within Vertica DB.
Thanks,
-
- Newbie
- Posts: 2
- Joined: Tue Nov 19, 2013 7:41 pm
Re: Errors while running DBD
I think @sKwa is referring to the limits.conf at OS layer. If you are using Linux, search Google using keywords "Linux limits.conf" you should be able to find examples of how to increase the resource you needed to finish DBD. For example: http://linux.die.net/man/5/limits.conf
However, Vertica installer should have taken care of those changes already. I am running Vertica 6 on CentOS Linux and that is indeed the case - I can find entries in the /etc/security/limits.conf that are specific to Vertica (i.e. for user dbadmin)
So either check the last installation log file (under /opt/vertica) or install the server again and see if there is some warnings you missed.
However, Vertica installer should have taken care of those changes already. I am running Vertica 6 on CentOS Linux and that is indeed the case - I can find entries in the /etc/security/limits.conf that are specific to Vertica (i.e. for user dbadmin)
So either check the last installation log file (under /opt/vertica) or install the server again and see if there is some warnings you missed.