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
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.
Dear all,
We have deployed a new cloudstack platform based on 4.9 version. Our primary
storage is based on glusterFS. Everything seemed ok (imported a centos7
template from our old Cloudstack deployment and deployed VMs).
However we are having trouble downloading templates (this implies
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
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 seconds for our CloudStack to reply,
resulting in time-out.
2016-11-06 03:40:42,891 DEBUG [c.c.a.ApiServlet] (http-8080-2:ctx-faa0bcbd)
(logid:86b581fc) ===START=== X.X.X.X