We upgraded to 3.3.0 early june and all data collection appeared fine. However, at the start of July when we tried to run the monthly report for June, the appliance just sits there at 100% CPU and report never returns.
I've just upgraded to 3.3.1 but outcome appears to be the same:
top - 14:37:07 up 11 min, 1 user, load average: 1.00, 1.07, 0.68
Tasks: 89 total, 2 running, 87 sleeping, 0 stopped, 0 zombie
Cpu(s): 99.7%us, 0.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 3619928k total, 1676960k used, 1942968k free, 18876k buffers
Swap: 2105340k total, 0k used, 2105340k free, 1175632k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4065 postgres 20 0 101m 47m 35m R 99.2 1.3 9:14.02 postgres
Any thoughts before I raise a support case?
Looks like it the valid query running in postgres.
usgmtr=# select query from pg_stat_activity ;
query
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Select +
sum(capped("Sample2"."vmBillingMemory",$1)) as "c0" +
From +
"SampleToLicense" "SampleToLicense1", +
"Sample" "Sample2", +
"Collection" "Collection3", +
"Vm" "Vm4", +
"HostLatest" "HostLatest5", +
"License" "License6" +
Where +
((("SampleToLicense1"."vmId" in ((Select +
"CustomerVm9"."vmId" as "CustomerVm9_vmId" +
From +
"CustomerVm" "CustomerVm9", +
"CustomerVmRule" "CustomerVmRule10" +
Where +
(("CustomerVmRule10"."createdBy" = $2) and ("CustomerVm9"."customerVmRuleId" = "CustomerVmRule10"."id")) +
) )) and (betweenco("SampleToLicense1"."start",$3,$4) and "SampleToLicense1"."reportExclusionReason" is null)) and ("SampleToLicense1"."sampleId" = "Sample2"."id"))