Re: Long delay in listDomains API response

Thanks Sergey, appreciate your reply. Points noted. Cheers. On Mon, Nov 7, 2016 at 10:44 AM, Sergey Levitskiy < sergey.levits...@autodesk.com> wrote: > What essentially happens here that for each domain, you have access with > your key, ACS executes 12 queries to get domain limits. Even if

Re: Long delay in listDomains API response

What essentially happens here that for each domain, you have access with your key, ACS executes 12 queries to get domain limits. Even if such query for each resource limit takes 0.03 sec it translates into 0.4 sec for each domain. If you have more than few domains, you will see rather lengthy

Re: Long delay in listDomains API response

Hi Wei, Thanks for your reply. Is it possible for us to remove the resource limitation feature -- any global settings that we can set to turn this off? If not, would you be able to let us know where on the source code this is being set, so that we can try changing it and recompile ACS to turn off

Re: Long delay in listDomains API response

I cannot say it is unnecessary or not for now. There are indeed many db connections when get resource limtiation/count of domains. A workaound is (1) listDomainChildren gets id of domain and sub-domains, then (2) listDomains with specified id. -Wei 2016-11-06 17:23 GMT+01:00 Cloud List

Re: Long delay in listDomains API response

Hi Sergey, Thanks for your reply. The grep result is a bit long, total 64K lines, so I have uploaded it here: https://dl.dropboxusercontent.com/u/24788636/ctx-3f3ff343.txt It seems there are a lot of unnecessary creating and closing of connections to the DB, causing the delay? Looking forward

Re: Long delay in listDomains API response

Can you grep for this line ‘ctx-3f3ff343’ in your log and post it here? On 11/5/16, 11:01 PM, "Cloud List" wrote: Dear all, After researching further, I found out that our problem is exactly the one reported on this JIRA bug:

Re: Long delay in listDomains API response

Dear all, After researching further, I found out that our problem is exactly the one reported on this JIRA bug: https://issues.apache.org/jira/browse/CLOUDSTACK-9405 I am cc-ing dsclose and Wei Zhou on this email. Anyone know if there's any resolution to the above problem/bug? On the bug

Re: Long delay in listDomains API response

Thanks Sergey for your assistance. I have enabled the TRACE logs as requested. After the listDomains API call, I see a lot of DB connections being created to the database, preparing SELECT statements and then immediately being closed thereafter. This happens many many times in the loop in the

Re: Long delay in listDomains API response

Please change DEBUG to TRACE for the following classes so they look like below. You don’t need to restart Cloudstack since it will dynamically switch log level. Once switched it will start generating enormous amount of logging so once you capture the slowness switch it back to DEBUG.

Re: Long delay in listDomains API response

You will probably need to enable TRACE logging and see what SQL query took long time to execute. On 11/5/16, 1:21 PM, "Cloud List" wrote: Hi, We have upgraded ACS from 4.2 to 4.8.1.1. We noted that a "listDomains" API call from our billing system took 21