cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael Weingärtner <rafaelweingart...@gmail.com>
Subject Re: Very long time to destroy VM
Date Wed, 13 Apr 2016 13:20:55 GMT
What hypervisor are you using?

Every single VM in your environment is presenting this behavior?



On Wed, Apr 13, 2016 at 10:18 AM, Simon Godard <sgodard@cloudops.com> wrote:

> Hi,
>
> I am trying to understand why a destroyVirtualMachine API call would take
> around 1 hour to get a successful async job result. From CloudStack log, I
> can see that the StopVmCmd occurred right away, but the DestroyVmCmd took 1
> hour to complete.
>
> Do you know what could cause such delays?
>
> The only suspicious log entries before the 1 hour delay are:
>
> 2016-04-11 15:23:32,896 DEBUG [com.cloud.vm.VirtualMachineManagerImpl]
> (API-Job-Executor-11:ctx-2a68671a job-1480365 ctx-a0c26dd1) Destroying vm
> VM[User|i-2278-11598-VM]
> 2016-04-11 15:23:32,920 WARN [com.cloud.utils.db.Merovingian2]
> (API-Job-Executor-11:ctx-2a68671a job-1480365 ctx-a0c26dd1) Was unable to
> find lock for the key vm_instance11598 and thread id 1817738544
>
> Then 1 hour later:
> 2016-04-11 16:23:36,839 DEBUG [com.cloud.capacity.CapacityManagerImpl]
> (API-Job-Executor-11:ctx-2a68671a job-1480365 ctx-a0c26dd1) VM state
> transitted from :Stopped to Destroyed with event: DestroyRequestedvm's
> original host id: 111 new host id: null host id before state transition:
> null
>
> Thanks!
> Simon Godard
>



-- 
Rafael Weingärtner

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message