cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Vazquez (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-9407) vm_network_map table doesnt get cleaned up properly
Date Mon, 06 Jun 2016 19:58:21 GMT


Nicolas Vazquez updated CLOUDSTACK-9407:
    Summary: vm_network_map table doesnt get cleaned up properly  (was: vm_network_map table
doesnt get cleanup properly)

> vm_network_map table doesnt get cleaned up properly
> ---------------------------------------------------
>                 Key: CLOUDSTACK-9407
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>            Assignee: Nicolas Vazquez
>             Fix For: 4.9.0
> h3. Introduction
> It was found out that in production environments {{vm_network_map}} table entries were
slowly growing. It was investigated how this entries were cleaned up.
> h3. Behaviour
> On vm creation, vm mappings are inserted on {{vm_network_map}}.
> On vm stop, mappings are deleted from {{vm_network_map}} for vm, as a result of the release
of its nics.
> h3. Problem
> If created vm is stopped from hypervisor side (at least on vSphere in which we tested
it), when CloudStack realizes vm is stopped it doesn't clean up {{vm_network_table}}, and,
as cleanup is made during vm stop, when vm is eventually destroyed and expunged it won't clean
up their entries in that table.
> h3. Proposed solution
> We propose to move {{vm_network_map}} table cleanup to expunge command instead of stop

This message was sent by Atlassian JIRA

View raw message