cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4620) Vm failed to start on the host on which it was running due to not having enough reservedMem when the host was powered on after being shutdown.
Date Thu, 12 Dec 2013 00:46:07 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prachi Damle resolved CLOUDSTACK-4620.
--------------------------------------

    Resolution: Won't Fix

Won't Fix since this situation gets corrected by the CapacityChecker thread.

> Vm failed to start on the host on which it was running due to not having enough reservedMem
when the host was powered on after being shutdown.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4620
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4620
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1
>         Environment: Build from 4.2-forward
>            Reporter: Sangeetha Hariharan
>            Assignee: Prachi Damle
>             Fix For: 4.3.0
>
>         Attachments: hostdown.rar
>
>
> Vm failed to start on the host on which it was running due to no having enough reservedMem
when the host was powered on after being shutdown
> Steps to reproduce the problem:
> Advanced zone with 1 cluster having 1 host (Xenserver).
> Had SSVM,CCPVM, 2 routers and few user Vms running in the host.
> Power down the host. 
> After few hours, powered on the host.
> All the Vms running on this host were marked "Stopped".
> Tried to start all the user Vms running in this host.
> 1 of the user Vms fails to start because of not having enough "Reserved RAM"
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) Reserved RAM: 0 , Requested RAM: 536870912
> When i tried to start the same Vm  again after few minutes , it started successfully
on the same host.
> Seems like there is some issue with releasing the capacity when all the Vms get marked
as "Stopped" by VM sync process.
> Vm that failed to start because of capacity and then eventually succeeded when starting
after few minutes is "temfromsnap" .
> Management server logs when starting the VM fails to start in the last_host_id.
> 2013-09-05 12:52:44,934 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) DeploymentPlanner allocation algorithm: com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_b297c61
> b@7e43d432
> 2013-09-05 12:52:44,934 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) Trying to allocate a host and storage pools from dc:1, pod:1,cluster:1,
requested cpu: 500, requested
>  ram: 536870912
> 2013-09-05 12:52:44,934 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) Is ROOT volume READY (pool already allocated)?: Yes
> 2013-09-05 12:52:44,934 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) This VM has last host_id specified, trying to choose the same host:
1
> 2013-09-05 12:52:44,938 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) Checking if host: 1 has enough capacity for requested CPU: 500 and requested
RAM: 536870912 , cpuOverprovisio
> ningFactor: 1.0
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) Hosts's actual total CPU: 9040 and CPU after applying overprovisioning:
9040
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) We need to allocate to the last host again, so checking if there is enough
reserved capacity
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) Reserved CPU: 1500 , Requested CPU: 500
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) Reserved RAM: 0 , Requested RAM: 536870912
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) STATS: Failed to alloc resource from host: 1 reservedCpu: 1500, requested
cpu: 500, reservedMem: 0, requested
>  mem: 536870912
> 2013-09-05 12:52:44,940 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533
> 186b3cbed ]) Host does not have enough reserved RAM available, cannot allocate to this
host.
> 2013-09-05 12:52:44,940 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) The last host of this VM does not have enough capacity
> 2013-09-05 12:52:44,940 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) Cannot choose the last host to deploy this VM
> 2013-09-05 12:52:44,940 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533186b3c
> bed ]) Searching resources only under specified Cluster: 1
> 2013-09-05 12:52:44,943 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-a441-533186b3c
> bed ]) Cannot allocate cluster list [1] for vm creation since their allocated percentage
crosses the disable capacity thre
> shold defined at each cluster/ at global value for capacity Type : 1, skipping these
clusters
> 2013-09-05 12:52:44,948 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-26:job-84
= [ ac245729-bfda-4e77-
> a441-533186b3cbed ]) Deploy avoids pods: [], clusters: [1], hosts: []



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message