VM instances not removed from cloud.vm_instance tabl

16 octobre 2012 22:21

VM instances not removed from cloud.vm_instance tabl

We have configured the expunge.delay and expunge.interval settings to 300 but VM instances are not being removed from the vm_instance table in the Cloud DB. The state shows "expunging" and the removed column is populated with the date and time when the VM was deleted by the user. Is the vm_instance suppose to keep these rows forever? I was expecting these rows to be deleted at some point.

Kevin Dorle MEMBERS 16 October 2012 - 22:21 PM

2 commentaires

Vous devez vous connecter pour laisser un commentaire.

Previous 2 commentaires

Date Votes

Pankaj Paliwal

23 mars 2016 07:09

VM instances not removed from cloud.vm_instance tabl

Hi,

This is by design. "expunging" is the last state in a VM life cycle. The record for the VM will exists in the "vm_instance table" in Cloud DB for future reference.

The way to confirm if a VM and the associated objects have indeed been removed (garbage collected) is to look at the "removed" column/field in the "vm_instance" table. In case it has a date then the the particular VM and associated objects (at least metadata) has been removed. If it is null then they still exists.

Hope this clarifies.

Regards,
Somesh

Somesh Naidu CITRIX EMPLOYEES 17 October 2012 - 04:32 AM

Pankaj Paliwal

23 mars 2016 07:09

Thanks Someshn. It might make sense to change the state in the vm_instance table to "expunged" to indicate the process is complete. The term "expunging" implies the process is still working.

Kevin Dorle MEMBERS 17 October 2012 - 13:31 PM