Good catch.
vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor was set
to True and mem.overprovisioning.factor is at 1.5.
This particular new pod has only two clusters at the moment.
Thanks a lot
On Sun, Mar 27, 2022 at 12:46 PM Rafael Weingärtner <
rafaelweingart...@gmail.com>
Are you using overprovisioning?
Em sáb., 26 de mar. de 2022 21:30, Curious Pandora
escreveu:
> After some further looking round and testing i am providing my findings.
>
> After monitoring all the database queries it is confirmed that the proper
> sevice_offering is returned back to the job.
> T
After some further looking round and testing i am providing my findings.
After monitoring all the database queries it is confirmed that the proper
sevice_offering is returned back to the job.
The values are correct and double checked.
By increasing the ram_size in the database to 512 from 256 the
Yes. I already confirmed that.
+-+
| service_offering_id |
+-+
| 22 |
+-+
++--+---+--+-+-++---+--+-+--+--+-+
Hi,
Can you check the database to see if the service offering is correct ?
select service_offering_id from vm_instance where id=1410;
select * from service_offering where id=;
-Wei
On Thu, 24 Mar 2022 at 09:23, Curious Pandora wrote:
> Hello all,
>
> After dedicating a pod for system vms (m
