[
https://issues.apache.org/jira/browse/CLOUDSTACK-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384053#comment-15384053
]
ASF subversion and git services commented on CLOUDSTACK-9407:
-------------------------------------------------------------
Commit 9be93c6e9022f35a2cd3dab6a099d69a77dd72ff in cloudstack's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9be93c6 ]
Merge pull request #1594 from nvazquez/vmnetworkmapissue
CLOUDSTACK-9407: vm_network_map table doesnt get cleaned up properlyJIRA
TICKET: https://issues.apache.org/jira/browse/CLOUDSTACK-9407
### 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.
### 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.
### 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.
### Proposed solution
We propose to move `vm_network_map` table cleanup to expunge command instead of
stop command.
* pr/1594:
CLOUDSTACK-9407: Refactor
CLOUDSTACK-9407: Release network resources on expunge command
Signed-off-by: Will Stevens <[email protected]>
> vm_network_map table doesnt get cleaned up properly
> ---------------------------------------------------
>
> Key: CLOUDSTACK-9407
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9407
> 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 command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
