Maybe it's because of that exception:
ERROR [c.c.a.AlertManagerImpl] (CapacityChecker:ctx-334ac971) Caught exception
in recalculating capacity
java.lang.NullPointerException
at
com.cloud.capacity.CapacityManagerImpl.updateCapacityForHost(CapacityManagerImpl.java:649)
at
com.cloud.alert.AlertManagerImpl.recalculateCapacity(AlertManagerImpl.java:282)
at
com.cloud.alert.AlertManagerImpl.checkForAlerts(AlertManagerImpl.java:434)
at
com.cloud.alert.AlertManagerImpl$CapacityChecker.runInContext(AlertManagerImpl.java:424)
at
org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Kind regards,
Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.
T: +31 20 316 0235
M:
E: [email protected]
W: http://www.leaseweb.com
Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
-----Original Message-----
From: Ilia Shakitko [mailto:[email protected]]
Sent: vrijdag, 07 november, 2014 15:50
To: [email protected]
Subject: RE: [CAPACITY STATS][4.4] - Primary storage is 0 + strange behaviour
on different VM statuses
Hi Lucian,
I am looking to it few days playing with VMs. So yes, I did :)
Kind regards,
Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.
T: +31 20 316 0235
M:
E: [email protected]
W: http://www.leaseweb.com
Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
-----Original Message-----
From: Nux! [mailto:[email protected]]
Sent: vrijdag, 07 november, 2014 14:34
To: [email protected]
Subject: Re: [CAPACITY STATS][4.4] - Primary storage is 0 + strange behaviour
on different VM statuses
Ilia,
There might be scheduled jobs to calculate and update usage stats, not sure
about this. Have you tried leaving it some more time between operations? Like,
kill the VM or whatever operations you want in the evening and see if the stats
are correct the next day.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Ilia Shakitko" <[email protected]>
> To: [email protected]
> Sent: Wednesday, 5 November, 2014 12:49:41
> Subject: [CAPACITY STATS][4.4] - Primary storage is 0 + strange
> behaviour on different VM statuses
> Hello,
>
> I am experiencing new features in ACS 4.4 and playing with VMs and
> ComputeOfferings to see what I can do. And I noticed 2 strange things.
>
> First of all. Whatever status a VM has – I can’t see Primary Storage is used:
> http://clip2net.com/s/jdOCBQ
>
> At second I made this experiment:
> 1) VM is Running: Amount of allocated resoures is X
> 2) Stop VM: Amount of alloc.resources is still X
> 3) Destroy VM: Amount of alloc.resources drops to Y
> 4) Recover VM (it is in stopped state now): Amount of allo.resources
> is still Y
> - WHAT?!
>
> * I am checking numbers in both places (pie charts and full capacity
> stats)
>
>
> I think something is wrong here. Isn’t it?
>
> Kind regards,
>
> Ilia Shakitko
> Innovation Engineer
> LeaseWeb Technologies B.V.
>
> T: +31 20 316 0235
>
> E: [email protected]
> W: www.leaseweb.com<http://www.leaseweb.com>
>
> Luttenbergweg 8, 1101 EC Amsterdam, Netherlands
