How to expunge a system VM volume without a system VM running?
Hi, This applies to CloudStack 4.6. The scenario: have one zone installed, and you want to delete the zone. Doing this requires deletion of everything under the host. When the system VMs are destroyed, their volumes go into Destroy state. The storage cleanup thread is constantly trying to expunge them, but it cannot since there's no system VM API endpoint. The message in the logs is: "No remote endpoint to send DeleteCommand, check if host or ssvm is down?" Since the volumes still technically exist, I was unable to delete the primary storage and the zone without editing the database. Is there a better way to do this? Or is this the officially recommended way? Thanks, Jeff
Re: Expunge-root volume
Thanks 2016-01-13 11:16 GMT+02:00 Erik Weber : > If it is deleted with Expunge it is deleted right away as far as I know. > Thus not recoverable. > > -- > Erik > > On Wed, Jan 13, 2016 at 10:12 AM, Semih Tolga DEMİR < > semihtolgade...@gmail.com> wrote: > > > Hi Erik, > > > > You right if do not check Expunge Root Volume is been there. But do u > have > > any idea, how i recover my VM after delete with Expunge? > > > > B.R. > > > > 2016-01-13 10:25 GMT+02:00 Erik Weber : > > > > > On Wed, Jan 13, 2016 at 9:10 AM, Semih Tolga DEMİR < > > > semihtolgade...@gmail.com> wrote: > > > > > > > Hi, > > > > > > > > I testing cloudstack, and i have a question about expunging. My > expunge > > > > interval = 1 day and when i delete my VM with Expunge > > > > > > > > > To the best of my knowledge, checking the 'Expunge' box means that you > > > would like to expunge it right away, e.g. not wait for the expunge > > thread. > > > > > > > > > > > > > i can not see ROOT > > > > part under Primary Storage->Volumes. But deleted VM's datadisk seem > > under > > > > Primary Storage->Volumes. > > > > > > > > Why there is not seen Root Volume, and how i can keep root volume > under > > > > Primary Storage->Volumes and recover the deleted VM? > > > > > > > > > > Simply don't check the 'Expunge' checkbox > > > > > > -- > > > Erik > > > > > >
Re: Expunge-root volume
If it is deleted with Expunge it is deleted right away as far as I know. Thus not recoverable. -- Erik On Wed, Jan 13, 2016 at 10:12 AM, Semih Tolga DEMİR < semihtolgade...@gmail.com> wrote: > Hi Erik, > > You right if do not check Expunge Root Volume is been there. But do u have > any idea, how i recover my VM after delete with Expunge? > > B.R. > > 2016-01-13 10:25 GMT+02:00 Erik Weber : > > > On Wed, Jan 13, 2016 at 9:10 AM, Semih Tolga DEMİR < > > semihtolgade...@gmail.com> wrote: > > > > > Hi, > > > > > > I testing cloudstack, and i have a question about expunging. My expunge > > > interval = 1 day and when i delete my VM with Expunge > > > > > > To the best of my knowledge, checking the 'Expunge' box means that you > > would like to expunge it right away, e.g. not wait for the expunge > thread. > > > > > > > > > i can not see ROOT > > > part under Primary Storage->Volumes. But deleted VM's datadisk seem > under > > > Primary Storage->Volumes. > > > > > > Why there is not seen Root Volume, and how i can keep root volume under > > > Primary Storage->Volumes and recover the deleted VM? > > > > > > > Simply don't check the 'Expunge' checkbox > > > > -- > > Erik > > >
Re: Expunge-root volume
Hi Erik, You right if do not check Expunge Root Volume is been there. But do u have any idea, how i recover my VM after delete with Expunge? B.R. 2016-01-13 10:25 GMT+02:00 Erik Weber : > On Wed, Jan 13, 2016 at 9:10 AM, Semih Tolga DEMİR < > semihtolgade...@gmail.com> wrote: > > > Hi, > > > > I testing cloudstack, and i have a question about expunging. My expunge > > interval = 1 day and when i delete my VM with Expunge > > > To the best of my knowledge, checking the 'Expunge' box means that you > would like to expunge it right away, e.g. not wait for the expunge thread. > > > > > i can not see ROOT > > part under Primary Storage->Volumes. But deleted VM's datadisk seem under > > Primary Storage->Volumes. > > > > Why there is not seen Root Volume, and how i can keep root volume under > > Primary Storage->Volumes and recover the deleted VM? > > > > Simply don't check the 'Expunge' checkbox > > -- > Erik >
Re: Expunge-root volume
On Wed, Jan 13, 2016 at 9:10 AM, Semih Tolga DEMİR < semihtolgade...@gmail.com> wrote: > Hi, > > I testing cloudstack, and i have a question about expunging. My expunge > interval = 1 day and when i delete my VM with Expunge To the best of my knowledge, checking the 'Expunge' box means that you would like to expunge it right away, e.g. not wait for the expunge thread. > i can not see ROOT > part under Primary Storage->Volumes. But deleted VM's datadisk seem under > Primary Storage->Volumes. > > Why there is not seen Root Volume, and how i can keep root volume under > Primary Storage->Volumes and recover the deleted VM? > Simply don't check the 'Expunge' checkbox -- Erik
Expunge-root volume
Hi, I testing cloudstack, and i have a question about expunging. My expunge interval = 1 day and when i delete my VM with Expunge i can not see ROOT part under Primary Storage->Volumes. But deleted VM's datadisk seem under Primary Storage->Volumes. Why there is not seen Root Volume, and how i can keep root volume under Primary Storage->Volumes and recover the deleted VM? Best Regards.
Re: Expunge
ountId":2,"format":"QCOW2","provisioningType":"THIN","id":138,"deviceId":0,"hypervisorType":"KVM"}},"wait":0}}]
}
2015-09-25 08:35:44,443 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-10:null) Seq 1-227431781184501: Processing: {
Ans: , MgmtId: 191612618435011, via: 1, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}] }
2015-09-25 08:35:44,443 DEBUG [c.c.a.t.Request]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Seq
1-227431781184501: Received: { Ans: , MgmtId: 191612618435011, via:
1, Ver: v1, Flags: 10, { Answer } }
2015-09-25 08:35:44,564 INFO [o.a.c.s.v.VolumeServiceImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Volume 138 is
not referred anywhere, remove it from volumes table
2015-09-25 08:35:44,852 DEBUG [c.c.v.VirtualMachineManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Expunged
VM[User|i-2-85-VM]
2015-09-25 08:35:44,942 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Access granted
to Acct[89b1af9a-23d4-11e5-83b6-048d3840e222-admin] to Domain:1/ by
AffinityGroupAccessChecker
2015-09-25 08:35:45,030 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Starting
cleaning up vm VM[User|i-2-85-VM] resources...
2015-09-25 08:35:45,032 INFO [c.c.n.s.SecurityGroupManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Disassociated
1 network groups from uservm 85
2015-09-25 08:35:45,131 DEBUG [c.c.n.s.SecurityGroupManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Security group
mappings are removed successfully for vm id=85
2015-09-25 08:35:45,200 DEBUG [c.c.n.f.FirewallManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) No firewall
rules are found for vm id=85
2015-09-25 08:35:45,276 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Firewall rules
are removed successfully as a part of vm id=85 expunge
2015-09-25 08:35:45,277 DEBUG [c.c.n.r.RulesManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) No port
forwarding rules are found for vm id=85
2015-09-25 08:35:45,277 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Port
forwarding rules are removed successfully as a part of vm id=85 expunge
2015-09-25 08:35:45,278 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Removed vm
id=85 from all load balancers as a part of expunge process
2015-09-25 08:35:45,278 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Successfully
cleaned up vm VM[User|i-2-85-VM] resources as a part of expunge process
2015-09-25 08:35:45,409 INFO [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-8b683ae7) Begin cleanup expired async-jobs
2015-09-25 08:35:45,411 INFO [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-8b683ae7) End cleanup expired async-jobs
2015-09-25 08:35:45,444 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Complete async
job-1014, jobStatus: SUCCEEDED, resultCode: 0, result:
org.apache.cloudstack.api.response.UserVmResponse/null/{"securitygroup":[],"nic":[],"tags":[],"affinitygroup":[]}
2015-09-25 08:35:45,445 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Publish async
job-1014 complete on message bus
2015-09-25 08:35:45,445 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Wake up jobs
related to job-1014
2015-09-25 08:35:45,445 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Update db
status for job-1014
2015-09-25 08:35:45,445 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014 ctx-85a6409c) Wake up jobs
joined with job-1014 and disjoin all subjobs created from job- 1014
2015-09-25 08:35:45,523 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-55:ctx-2e9eb037 job-1014) Done executing
org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin for
job-1014
2015-09-25 08:35:45,523 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-55:ctx-2e9eb037 job-1014) Remove job-1014 from job
monitoring
2015-09-25 08:35:46,231 DEBUG [c.c.a.ApiServlet]
(catalina-exec-3:ctx-51adc6ae) ===START=== 10.0.8.6 -- GET
command=queryAsyncJobResult&jobId=605e1db3-f3a6-4b7e-b62c-00ccc65944df&response=json&_=1443184546234
2015-09-25 08:35:46,326 DEBUG [c.c.a.ApiServlet]
(catalina-exec-3:ctx-51adc6ae ctx-eafb69bc) ===END=== 10.0.8.6 -- GET
command=queryAsyncJobResult&jobId=605e1db3-f3a6-4b7e-b62c-00ccc65944df&response=json&_=1443184546234
2015-09-25 08:35:46,57
Re: Expunge
Luis, Do you use shared mount point with your KVM hypervisor or local NFS server? I have tested "Expunge" at my CS 4.5.3 and when I delete VM with "expunge" option -- Cloudstack deletes it from the storage immediately. Can you do the same test and look into management log file ? It would be nice to see trace from what is going on. Or do you have problem only with delayed "expunge" ? Vadim. On 2015-09-24 21:04, Luis wrote: Hi Thank you for your answer. I am using CL 4.5.2 with KVM in Raid 5, after a month the space was not freed up, previously i changes the expunge to 100 - FROM: Vadim Kimlaychuk TO: Luis CC: users@cloudstack.apache.org SENT: Thursday, September 24, 2015 1:33 PM SUBJECT: Re: Expunge Hello Luis, If I remember correctly - you don't get it freed immediately. There is some background process that cleans up. You can probably get better response if write down what version of CS, hypervisor and storage type are you using. Regards, Vadim On 2015-09-24 14:25, Luis wrote: Hi I notice that when I Expunge VM the hard disk space is not returned, I still have the same use, I had to deleted manually from the raid, is this a bug or I am missing a comfiguration?
Re: Expunge
Hello Luis, If I remember correctly - you don't get it freed immediately. There is some background process that cleans up. You can probably get better response if write down what version of CS, hypervisor and storage type are you using. Regards, Vadim On 2015-09-24 14:25, Luis wrote: Hi I notice that when I Expunge VM the hard disk space is not returned, I still have the same use, I had to deleted manually from the raid, is this a bug or I am missing a comfiguration?
Expunge
Hi I notice that when I Expunge VM the hard disk space is not returned, I still have the same use, I had to deleted manually from the raid, is this a bug or I am missing a comfiguration?
RE: expunge disk issue
That's VM expunge. For storage you should check storage.*.cleanup.* global settings. I am hoping these are enabled. What Prashant is pointing at is for you to verify free space after capacity checker thread has run so CCP has the updated capacity. When you say storage do you refer to primary or secondary storage? Anyway, I am wondering if are you seeing disks on the storage that are stale (orphan) by a large margin, like few days/months, not getting cleared? Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: Jochim, Ingo [mailto:ingo.joc...@bautzen-it.de] Sent: Thursday, January 22, 2015 2:51 AM To: 'users@cloudstack.apache.org' Subject: AW: expunge disk issue Right. Here are our settings: Expunge.delay=21600 Expunge.interval=3600 Expunge.workers=4 The disks have been deleted/moved a week ago. Nothing happened so far. Regards, Ingo -Ursprüngliche Nachricht- Von: Prashant Kumar Mishra [mailto:prashantkumar.mis...@citrix.com] Gesendet: Donnerstag, 22. Januar 2015 08:11 An: users@cloudstack.apache.org Betreff: Re: expunge disk issue You should see free space after capacity.check.period which is in global Settings ~prashant On 1/22/15, 12:32 PM, "Jochim, Ingo" wrote: >Hi all, > >we are close to our capacity limit on the storage. >We noticed that deleting virtual disks within CS (4.2) never does free >up space on the storage side. >Same for disk migration. >We reduced the expunge time but nothing happens. >Is there procedure to trigger this and check the status/progress? > >Thanks, >Ingo > >-- >This email was Virus checked by Astaro Security Gateway. >http://www.sophos.com -- This email was Virus checked by Astaro Security Gateway. http://www.sophos.com
AW: expunge disk issue
Right. Here are our settings: Expunge.delay=21600 Expunge.interval=3600 Expunge.workers=4 The disks have been deleted/moved a week ago. Nothing happened so far. Regards, Ingo -Ursprüngliche Nachricht- Von: Prashant Kumar Mishra [mailto:prashantkumar.mis...@citrix.com] Gesendet: Donnerstag, 22. Januar 2015 08:11 An: users@cloudstack.apache.org Betreff: Re: expunge disk issue You should see free space after capacity.check.period which is in global Settings ~prashant On 1/22/15, 12:32 PM, "Jochim, Ingo" wrote: >Hi all, > >we are close to our capacity limit on the storage. >We noticed that deleting virtual disks within CS (4.2) never does free >up space on the storage side. >Same for disk migration. >We reduced the expunge time but nothing happens. >Is there procedure to trigger this and check the status/progress? > >Thanks, >Ingo > >-- >This email was Virus checked by Astaro Security Gateway. >http://www.sophos.com -- This email was Virus checked by Astaro Security Gateway. http://www.sophos.com
Re: expunge disk issue
You should see free space after capacity.check.period which is in global Settings ~prashant On 1/22/15, 12:32 PM, "Jochim, Ingo" wrote: >Hi all, > >we are close to our capacity limit on the storage. >We noticed that deleting virtual disks within CS (4.2) never does free up >space on the storage side. >Same for disk migration. >We reduced the expunge time but nothing happens. >Is there procedure to trigger this and check the status/progress? > >Thanks, >Ingo > >-- >This email was Virus checked by Astaro Security Gateway. >http://www.sophos.com
Re: expunge disk issue
You should see free space after capacity.check.period which is in global settings On 1/22/15, 12:32 PM, "Jochim, Ingo" wrote: >rigger this and check the status/progre
expunge disk issue
Hi all, we are close to our capacity limit on the storage. We noticed that deleting virtual disks within CS (4.2) never does free up space on the storage side. Same for disk migration. We reduced the expunge time but nothing happens. Is there procedure to trigger this and check the status/progress? Thanks, Ingo -- This email was Virus checked by Astaro Security Gateway. http://www.sophos.com
RE: force expunge disks
If you are 'sure' the volumes have been deleted from the Primary Storage, and you just want to clean up the references in the UI, then in the volumes table, update the 'state' column to 'Expunged' and add a date/time into the 'removed' column. You may also want to 'null' the 'last_pod_id' , 'folder' & pod_id, columns. I only say this as volumes which were successfully expunged did not have values in these columns. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Rafael Weingartner [mailto:rafaelweingart...@gmail.com] Sent: 22 January 2014 18:51 To: users@cloudstack.apache.org Subject: Re: force expunge disks is there any errors on MS logs? Could you post them here? On Wed, Jan 22, 2014 at 4:48 PM, Pierre-Luc Dion wrote: > The delete and expunge process work fine. it's just that for some > reason we have few disks which failed, I'm suspecting a primary > storage that would have been removed without emptied it. > > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, > 1101 > - - - > > *CloudOps*420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > > > On Wed, Jan 22, 2014 at 1:46 PM, Pierre-Luc Dion wrote: > >> Settings expunge.delay and expunge.interval have been set to 60 long >> time ago. I'm in the situation of a "kind of broken" system for now >> where in cloudstack some disks are in "Expunging" state but the VDI >> (.vhd file) itself as been deleted from the primary storage. >> >> >> Pierre-Luc Dion >> Architecte de Solution Cloud | Cloud Solutions Architect >> 514-447-3456, 1101 >> - - - >> >> *CloudOps* >> 420 rue Guy >> Montréal QC H3J 1S6 >> www.cloudops.com >> @CloudOps_ >> >> >> On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. < >> hollman.enc...@gmail.com> wrote: >> >>> You have to wait the interval configured on global settings: >>> >>> >>> expunge.delayDetermines how long (in seconds) to wait before actually >>> expunging destroyed vm. The default value = the default value of >>> expunge.interval >>> >>> >>> expunge.intervalThe interval (in seconds) to wait before running the >>> expunge thread. >>> >>> I can't remember the default time, i think that it's 42 hours. i >>> Change it to 1 hour (in seconds) >>> >>> and that's it >>> >>> >>> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion >>> >> >wrote: >>> >>> > I'm stuck with some disks with "Expunging" state. The the VDI for >>> > the hypervisor is gone but the disk in Cloudstack remain in >>> > Expunging >>> state. is >>> > their a way to force expunging them or updating the database to >>> > reflect the proper state of the disk ? >>> > >>> > I'm tempted to execute following SQL queries but would I miss >>> > entries somewhere else? >>> > >>> > update volumes set removed='2014-01-16 18:57:25', >>> > state='Expunged', >>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; update >>> > volume_view set removed='2014-01-16 18:57:25', state='Expunged', >>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >>> > >>> > >>> > Thanks, >>> > >>> > Pierre-Luc Dion >>> > Architecte de Solution Cloud | Cloud Solutions Architect >>> > 514-447-3456, 1101 >>> > - - - >>> > >>> > *CloudOps*420 rue Guy >>> > Montréal QC H3J 1S6 >>> > www.cloudops.com >>> > @CloudOps_ >>> > >>> >>> >>> >>> -- >>> Hollman Eduardo Enciso R. >>> http://nexxuz.com >>> http://algolibre.com <http://www.hollmanenciso.com/> @hollman >>> >> >> -- Rafael Weingärtner Need Enterprise Grade Support for Apache CloudStack? Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments. Apache CloudStack Bootcamp training courses **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/> 18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/> 17th-2
Re: force expunge disks
yes, Cloudstack management-server has been restart many times. Pierre-Luc Dion Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, 1101 - - - *CloudOps*420 rue Guy Montréal QC H3J 1S6 www.cloudops.com @CloudOps_ On Wed, Jan 22, 2014 at 1:48 PM, Rafael Weingartner < rafaelweingart...@gmail.com> wrote: > Have you restarted the cloudstack MS after you changed the parameters? > > On Wed, Jan 22, 2014 at 4:46 PM, Pierre-Luc Dion > wrote: > > Settings expunge.delay and expunge.interval have been set to 60 long time > > ago. I'm in the situation of a "kind of broken" system for now where in > > cloudstack some disks are in "Expunging" state but the VDI (.vhd file) > > itself as been deleted from the primary storage. > > > > > > Pierre-Luc Dion > > Architecte de Solution Cloud | Cloud Solutions Architect > > 514-447-3456, 1101 > > - - - > > > > *CloudOps*420 rue Guy > > Montréal QC H3J 1S6 > > www.cloudops.com > > @CloudOps_ > > > > > > On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. < > hollman.enc...@gmail.com > >> wrote: > > > >> You have to wait the interval configured on global settings: > >> > >> > >> expunge.delayDetermines how long (in seconds) to wait before > actually > >> expunging destroyed vm. The default value = the default value of > >> expunge.interval > >> > >> > >> expunge.intervalThe interval (in seconds) to wait before running the > >> expunge thread. > >> > >> I can't remember the default time, i think that it's 42 hours. i Change > it > >> to 1 hour (in seconds) > >> > >> and that's it > >> > >> > >> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion >> >wrote: > >> > >> > I'm stuck with some disks with "Expunging" state. The the VDI for the > >> > hypervisor is gone but the disk in Cloudstack remain in Expunging > state. > >> is > >> > their a way to force expunging them or updating the database to > reflect > >> > the proper state of the disk ? > >> > > >> > I'm tempted to execute following SQL queries but would I miss entries > >> > somewhere else? > >> > > >> > update volumes set removed='2014-01-16 18:57:25', state='Expunged', > >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; > >> > update volume_view set removed='2014-01-16 18:57:25', > state='Expunged', > >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; > >> > > >> > > >> > Thanks, > >> > > >> > Pierre-Luc Dion > >> > Architecte de Solution Cloud | Cloud Solutions Architect > >> > 514-447-3456, 1101 > >> > - - - > >> > > >> > *CloudOps*420 rue Guy > >> > Montréal QC H3J 1S6 > >> > www.cloudops.com > >> > @CloudOps_ > >> > > >> > >> > >> > >> -- > >> Hollman Eduardo Enciso R. > >> http://nexxuz.com > >> http://algolibre.com <http://www.hollmanenciso.com/> > >> @hollman > >> > > > > -- > Rafael Weingärtner >
Re: force expunge disks
Have you restarted the cloudstack MS after you changed the parameters? On Wed, Jan 22, 2014 at 4:46 PM, Pierre-Luc Dion wrote: > Settings expunge.delay and expunge.interval have been set to 60 long time > ago. I'm in the situation of a "kind of broken" system for now where in > cloudstack some disks are in "Expunging" state but the VDI (.vhd file) > itself as been deleted from the primary storage. > > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect > 514-447-3456, 1101 > - - - > > *CloudOps*420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > > > On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. > wrote: > >> You have to wait the interval configured on global settings: >> >> >> expunge.delayDetermines how long (in seconds) to wait before actually >> expunging destroyed vm. The default value = the default value of >> expunge.interval >> >> >> expunge.intervalThe interval (in seconds) to wait before running the >> expunge thread. >> >> I can't remember the default time, i think that it's 42 hours. i Change it >> to 1 hour (in seconds) >> >> and that's it >> >> >> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion > >wrote: >> >> > I'm stuck with some disks with "Expunging" state. The the VDI for the >> > hypervisor is gone but the disk in Cloudstack remain in Expunging state. >> is >> > their a way to force expunging them or updating the database to reflect >> > the proper state of the disk ? >> > >> > I'm tempted to execute following SQL queries but would I miss entries >> > somewhere else? >> > >> > update volumes set removed='2014-01-16 18:57:25', state='Expunged', >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged', >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >> > >> > >> > Thanks, >> > >> > Pierre-Luc Dion >> > Architecte de Solution Cloud | Cloud Solutions Architect >> > 514-447-3456, 1101 >> > - - - >> > >> > *CloudOps*420 rue Guy >> > Montréal QC H3J 1S6 >> > www.cloudops.com >> > @CloudOps_ >> > >> >> >> >> -- >> Hollman Eduardo Enciso R. >> http://nexxuz.com >> http://algolibre.com <http://www.hollmanenciso.com/> >> @hollman >> -- Rafael Weingärtner
Re: force expunge disks
is there any errors on MS logs? Could you post them here? On Wed, Jan 22, 2014 at 4:48 PM, Pierre-Luc Dion wrote: > The delete and expunge process work fine. it's just that for some reason we > have few disks which failed, I'm suspecting a primary storage that would > have been removed without emptied it. > > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect > 514-447-3456, 1101 > - - - > > *CloudOps*420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > > > On Wed, Jan 22, 2014 at 1:46 PM, Pierre-Luc Dion wrote: > >> Settings expunge.delay and expunge.interval have been set to 60 long time >> ago. I'm in the situation of a "kind of broken" system for now where in >> cloudstack some disks are in "Expunging" state but the VDI (.vhd file) >> itself as been deleted from the primary storage. >> >> >> Pierre-Luc Dion >> Architecte de Solution Cloud | Cloud Solutions Architect >> 514-447-3456, 1101 >> - - - >> >> *CloudOps* >> 420 rue Guy >> Montréal QC H3J 1S6 >> www.cloudops.com >> @CloudOps_ >> >> >> On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. < >> hollman.enc...@gmail.com> wrote: >> >>> You have to wait the interval configured on global settings: >>> >>> >>> expunge.delayDetermines how long (in seconds) to wait before actually >>> expunging destroyed vm. The default value = the default value of >>> expunge.interval >>> >>> >>> expunge.intervalThe interval (in seconds) to wait before running the >>> expunge thread. >>> >>> I can't remember the default time, i think that it's 42 hours. i Change it >>> to 1 hour (in seconds) >>> >>> and that's it >>> >>> >>> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion >> >wrote: >>> >>> > I'm stuck with some disks with "Expunging" state. The the VDI for the >>> > hypervisor is gone but the disk in Cloudstack remain in Expunging >>> state. is >>> > their a way to force expunging them or updating the database to reflect >>> > the proper state of the disk ? >>> > >>> > I'm tempted to execute following SQL queries but would I miss entries >>> > somewhere else? >>> > >>> > update volumes set removed='2014-01-16 18:57:25', state='Expunged', >>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >>> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged', >>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >>> > >>> > >>> > Thanks, >>> > >>> > Pierre-Luc Dion >>> > Architecte de Solution Cloud | Cloud Solutions Architect >>> > 514-447-3456, 1101 >>> > - - - >>> > >>> > *CloudOps*420 rue Guy >>> > Montréal QC H3J 1S6 >>> > www.cloudops.com >>> > @CloudOps_ >>> > >>> >>> >>> >>> -- >>> Hollman Eduardo Enciso R. >>> http://nexxuz.com >>> http://algolibre.com <http://www.hollmanenciso.com/> >>> @hollman >>> >> >> -- Rafael Weingärtner
Re: force expunge disks
The delete and expunge process work fine. it's just that for some reason we have few disks which failed, I'm suspecting a primary storage that would have been removed without emptied it. Pierre-Luc Dion Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, 1101 - - - *CloudOps*420 rue Guy Montréal QC H3J 1S6 www.cloudops.com @CloudOps_ On Wed, Jan 22, 2014 at 1:46 PM, Pierre-Luc Dion wrote: > Settings expunge.delay and expunge.interval have been set to 60 long time > ago. I'm in the situation of a "kind of broken" system for now where in > cloudstack some disks are in "Expunging" state but the VDI (.vhd file) > itself as been deleted from the primary storage. > > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect > 514-447-3456, 1101 > - - - > > *CloudOps* > 420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > > > On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. < > hollman.enc...@gmail.com> wrote: > >> You have to wait the interval configured on global settings: >> >> >> expunge.delayDetermines how long (in seconds) to wait before actually >> expunging destroyed vm. The default value = the default value of >> expunge.interval >> >> >> expunge.intervalThe interval (in seconds) to wait before running the >> expunge thread. >> >> I can't remember the default time, i think that it's 42 hours. i Change it >> to 1 hour (in seconds) >> >> and that's it >> >> >> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion > >wrote: >> >> > I'm stuck with some disks with "Expunging" state. The the VDI for the >> > hypervisor is gone but the disk in Cloudstack remain in Expunging >> state. is >> > their a way to force expunging them or updating the database to reflect >> > the proper state of the disk ? >> > >> > I'm tempted to execute following SQL queries but would I miss entries >> > somewhere else? >> > >> > update volumes set removed='2014-01-16 18:57:25', state='Expunged', >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged', >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; >> > >> > >> > Thanks, >> > >> > Pierre-Luc Dion >> > Architecte de Solution Cloud | Cloud Solutions Architect >> > 514-447-3456, 1101 >> > - - - >> > >> > *CloudOps*420 rue Guy >> > Montréal QC H3J 1S6 >> > www.cloudops.com >> > @CloudOps_ >> > >> >> >> >> -- >> Hollman Eduardo Enciso R. >> http://nexxuz.com >> http://algolibre.com <http://www.hollmanenciso.com/> >> @hollman >> > >
Re: force expunge disks
Settings expunge.delay and expunge.interval have been set to 60 long time ago. I'm in the situation of a "kind of broken" system for now where in cloudstack some disks are in "Expunging" state but the VDI (.vhd file) itself as been deleted from the primary storage. Pierre-Luc Dion Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, 1101 - - - *CloudOps*420 rue Guy Montréal QC H3J 1S6 www.cloudops.com @CloudOps_ On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. wrote: > You have to wait the interval configured on global settings: > > > expunge.delayDetermines how long (in seconds) to wait before actually > expunging destroyed vm. The default value = the default value of > expunge.interval > > > expunge.intervalThe interval (in seconds) to wait before running the > expunge thread. > > I can't remember the default time, i think that it's 42 hours. i Change it > to 1 hour (in seconds) > > and that's it > > > On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion >wrote: > > > I'm stuck with some disks with "Expunging" state. The the VDI for the > > hypervisor is gone but the disk in Cloudstack remain in Expunging state. > is > > their a way to force expunging them or updating the database to reflect > > the proper state of the disk ? > > > > I'm tempted to execute following SQL queries but would I miss entries > > somewhere else? > > > > update volumes set removed='2014-01-16 18:57:25', state='Expunged', > > display_volume=0 WHERE name='DATA-1442' LIMIT 1; > > update volume_view set removed='2014-01-16 18:57:25', state='Expunged', > > display_volume=0 WHERE name='DATA-1442' LIMIT 1; > > > > > > Thanks, > > > > Pierre-Luc Dion > > Architecte de Solution Cloud | Cloud Solutions Architect > > 514-447-3456, 1101 > > - - - > > > > *CloudOps*420 rue Guy > > Montréal QC H3J 1S6 > > www.cloudops.com > > @CloudOps_ > > > > > > -- > Hollman Eduardo Enciso R. > http://nexxuz.com > http://algolibre.com <http://www.hollmanenciso.com/> > @hollman >
Re: force expunge disks
You have to wait the interval configured on global settings: expunge.delayDetermines how long (in seconds) to wait before actually expunging destroyed vm. The default value = the default value of expunge.interval expunge.intervalThe interval (in seconds) to wait before running the expunge thread. I can't remember the default time, i think that it's 42 hours. i Change it to 1 hour (in seconds) and that's it On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion wrote: > I'm stuck with some disks with "Expunging" state. The the VDI for the > hypervisor is gone but the disk in Cloudstack remain in Expunging state. is > their a way to force expunging them or updating the database to reflect > the proper state of the disk ? > > I'm tempted to execute following SQL queries but would I miss entries > somewhere else? > > update volumes set removed='2014-01-16 18:57:25', state='Expunged', > display_volume=0 WHERE name='DATA-1442' LIMIT 1; > update volume_view set removed='2014-01-16 18:57:25', state='Expunged', > display_volume=0 WHERE name='DATA-1442' LIMIT 1; > > > Thanks, > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect > 514-447-3456, 1101 > - - - > > *CloudOps*420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > -- Hollman Eduardo Enciso R. http://nexxuz.com http://algolibre.com <http://www.hollmanenciso.com/> @hollman
force expunge disks
I'm stuck with some disks with "Expunging" state. The the VDI for the hypervisor is gone but the disk in Cloudstack remain in Expunging state. is their a way to force expunging them or updating the database to reflect the proper state of the disk ? I'm tempted to execute following SQL queries but would I miss entries somewhere else? update volumes set removed='2014-01-16 18:57:25', state='Expunged', display_volume=0 WHERE name='DATA-1442' LIMIT 1; update volume_view set removed='2014-01-16 18:57:25', state='Expunged', display_volume=0 WHERE name='DATA-1442' LIMIT 1; Thanks, Pierre-Luc Dion Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, 1101 - - - *CloudOps*420 rue Guy Montréal QC H3J 1S6 www.cloudops.com @CloudOps_
Re: Remote force expunge?
The default values for expunge.delay and expunge.interval is 10mins. Have you tried setting these to lower values? I don't think there is any minimum window, it is configurable. -Koushik On 26-Aug-2013, at 7:51 PM, David Matteson wrote: > Hi Travis, > > Wanting to provide a 10 minute (or longer) recovery time is exactly why I'm > looking for some way to force an expunge remotely on demand. > > The problem with providing a long recovery time is that a user cannot deploy > a new VM with the same hostname (or IP address) until the old one is > expunged. Thus the desire to be able to say "No I really don't want to > recover the old one, get rid of it so I can make a new one." > > It seems like an expungeDestroyedVirtualMachine API call might be in order? > > On 8/26/13 10:06 AM, Travis Graham wrote: >> Hey David, >> >> As far as I understand it, there is no way to immediately expunge a deleted >> VM easily. By design there's a minimum 10 minute window to allow the >> recovery of a VM once it has been deleted. >> >> If you wanted to remove all references from the database and manually remove >> the associated files on your primary and secondary storage, there's nothing >> stopping you from doing that, but you'd probably be best to set your >> expunge.delay and expunge.interval to 600 and let the system do the heavy >> lifting. >> >> Travis >> >> On Aug 26, 2013, at 9:35 AM, David Matteson wrote: >> >>> Hey everybody, >>> >>> Quick question; there is no API call for it, but does anybody know of a way >>> to force an expunge to run remotely? Ideally on a specific vmid. >>> >>> Thanks! >
RE: Remote force expunge?
Nice idea, +1 for it. --Sanjay > -Original Message- > From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com] > Sent: Monday, August 26, 2013 7:56 PM > To: users@cloudstack.apache.org > Subject: RE: Remote force expunge? > > +1 from me, why don't you log a feature request > > Regards > > Geoff Higginbottom > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 > > geoff.higginbot...@shapeblue.com > > -Original Message- > From: Kirk Jantzer [mailto:kirk.jant...@gmail.com] > Sent: 26 August 2013 10:24 > To: Cloudstack users mailing list > Subject: Re: Remote force expunge? > > I like that idea :-) > > > Regards, > > Kirk Jantzer > http://about.met/kirkjantzer > > > On Mon, Aug 26, 2013 at 10:21 AM, David Matteson > wrote: > > > Hi Travis, > > > > Wanting to provide a 10 minute (or longer) recovery time is exactly > > why I'm looking for some way to force an expunge remotely on demand. > > > > The problem with providing a long recovery time is that a user cannot > > deploy a new VM with the same hostname (or IP address) until the old > > one is expunged. Thus the desire to be able to say "No I really don't > > want to recover the old one, get rid of it so I can make a new one." > > > > It seems like an expungeDestroyedVirtualMachine API call might be in > order? > > > > > > On 8/26/13 10:06 AM, Travis Graham wrote: > > > >> Hey David, > >> > >> As far as I understand it, there is no way to immediately expunge a > >> deleted VM easily. By design there's a minimum 10 minute window to > >> allow the recovery of a VM once it has been deleted. > >> > >> If you wanted to remove all references from the database and manually > >> remove the associated files on your primary and secondary storage, > >> there's nothing stopping you from doing that, but you'd probably be > >> best to set your expunge.delay and expunge.interval to 600 and let > >> the system do the heavy lifting. > >> > >> Travis > >> > >> On Aug 26, 2013, at 9:35 AM, David Matteson > > >> wrote: > >> > >> Hey everybody, > >>> > >>> Quick question; there is no API call for it, but does anybody know > >>> of a way to force an expunge to run remotely? Ideally on a specific vmid. > >>> > >>> Thanks! > >>> > >> > > > This email and any attachments to it may be confidential and are intended > solely for the use of the individual to whom it is addressed. Any views or > opinions expressed are solely those of the author and do not necessarily > represent those of Shape Blue Ltd or related companies. If you are not the > intended recipient of this email, you must neither take any action based > upon its contents, nor copy or show it to anyone. Please contact the sender if > you believe you have received this email in error. Shape Blue Ltd is a > company incorporated in England & Wales. ShapeBlue Services India LLP is > operated under license from Shape Blue Ltd. ShapeBlue is a registered > trademark.
Re: Remote force expunge?
Will do :) On 8/26/13 10:25 AM, Geoff Higginbottom wrote: +1 from me, why don't you log a feature request Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Kirk Jantzer [mailto:kirk.jant...@gmail.com] Sent: 26 August 2013 10:24 To: Cloudstack users mailing list Subject: Re: Remote force expunge? I like that idea :-) Regards, Kirk Jantzer http://about.met/kirkjantzer On Mon, Aug 26, 2013 at 10:21 AM, David Matteson wrote: Hi Travis, Wanting to provide a 10 minute (or longer) recovery time is exactly why I'm looking for some way to force an expunge remotely on demand. The problem with providing a long recovery time is that a user cannot deploy a new VM with the same hostname (or IP address) until the old one is expunged. Thus the desire to be able to say "No I really don't want to recover the old one, get rid of it so I can make a new one." It seems like an expungeDestroyedVirtualMachine API call might be in order? On 8/26/13 10:06 AM, Travis Graham wrote: Hey David, As far as I understand it, there is no way to immediately expunge a deleted VM easily. By design there's a minimum 10 minute window to allow the recovery of a VM once it has been deleted. If you wanted to remove all references from the database and manually remove the associated files on your primary and secondary storage, there's nothing stopping you from doing that, but you'd probably be best to set your expunge.delay and expunge.interval to 600 and let the system do the heavy lifting. Travis On Aug 26, 2013, at 9:35 AM, David Matteson wrote: Hey everybody, Quick question; there is no API call for it, but does anybody know of a way to force an expunge to run remotely? Ideally on a specific vmid. Thanks! This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
RE: Remote force expunge?
+1 from me, why don't you log a feature request Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Kirk Jantzer [mailto:kirk.jant...@gmail.com] Sent: 26 August 2013 10:24 To: Cloudstack users mailing list Subject: Re: Remote force expunge? I like that idea :-) Regards, Kirk Jantzer http://about.met/kirkjantzer On Mon, Aug 26, 2013 at 10:21 AM, David Matteson wrote: > Hi Travis, > > Wanting to provide a 10 minute (or longer) recovery time is exactly > why I'm looking for some way to force an expunge remotely on demand. > > The problem with providing a long recovery time is that a user cannot > deploy a new VM with the same hostname (or IP address) until the old > one is expunged. Thus the desire to be able to say "No I really don't > want to recover the old one, get rid of it so I can make a new one." > > It seems like an expungeDestroyedVirtualMachine API call might be in order? > > > On 8/26/13 10:06 AM, Travis Graham wrote: > >> Hey David, >> >> As far as I understand it, there is no way to immediately expunge a >> deleted VM easily. By design there's a minimum 10 minute window to >> allow the recovery of a VM once it has been deleted. >> >> If you wanted to remove all references from the database and manually >> remove the associated files on your primary and secondary storage, >> there's nothing stopping you from doing that, but you'd probably be >> best to set your expunge.delay and expunge.interval to 600 and let >> the system do the heavy lifting. >> >> Travis >> >> On Aug 26, 2013, at 9:35 AM, David Matteson >> wrote: >> >> Hey everybody, >>> >>> Quick question; there is no API call for it, but does anybody know >>> of a way to force an expunge to run remotely? Ideally on a specific vmid. >>> >>> Thanks! >>> >> > This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: Remote force expunge?
I like that idea :-) Regards, Kirk Jantzer http://about.met/kirkjantzer On Mon, Aug 26, 2013 at 10:21 AM, David Matteson wrote: > Hi Travis, > > Wanting to provide a 10 minute (or longer) recovery time is exactly why > I'm looking for some way to force an expunge remotely on demand. > > The problem with providing a long recovery time is that a user cannot > deploy a new VM with the same hostname (or IP address) until the old one is > expunged. Thus the desire to be able to say "No I really don't want to > recover the old one, get rid of it so I can make a new one." > > It seems like an expungeDestroyedVirtualMachine API call might be in order? > > > On 8/26/13 10:06 AM, Travis Graham wrote: > >> Hey David, >> >> As far as I understand it, there is no way to immediately expunge a >> deleted VM easily. By design there's a minimum 10 minute window to allow >> the recovery of a VM once it has been deleted. >> >> If you wanted to remove all references from the database and manually >> remove the associated files on your primary and secondary storage, there's >> nothing stopping you from doing that, but you'd probably be best to set >> your expunge.delay and expunge.interval to 600 and let the system do the >> heavy lifting. >> >> Travis >> >> On Aug 26, 2013, at 9:35 AM, David Matteson >> wrote: >> >> Hey everybody, >>> >>> Quick question; there is no API call for it, but does anybody know of a >>> way to force an expunge to run remotely? Ideally on a specific vmid. >>> >>> Thanks! >>> >> >
Re: Remote force expunge?
Hi Travis, Wanting to provide a 10 minute (or longer) recovery time is exactly why I'm looking for some way to force an expunge remotely on demand. The problem with providing a long recovery time is that a user cannot deploy a new VM with the same hostname (or IP address) until the old one is expunged. Thus the desire to be able to say "No I really don't want to recover the old one, get rid of it so I can make a new one." It seems like an expungeDestroyedVirtualMachine API call might be in order? On 8/26/13 10:06 AM, Travis Graham wrote: Hey David, As far as I understand it, there is no way to immediately expunge a deleted VM easily. By design there's a minimum 10 minute window to allow the recovery of a VM once it has been deleted. If you wanted to remove all references from the database and manually remove the associated files on your primary and secondary storage, there's nothing stopping you from doing that, but you'd probably be best to set your expunge.delay and expunge.interval to 600 and let the system do the heavy lifting. Travis On Aug 26, 2013, at 9:35 AM, David Matteson wrote: Hey everybody, Quick question; there is no API call for it, but does anybody know of a way to force an expunge to run remotely? Ideally on a specific vmid. Thanks!
Re: Remote force expunge?
Hey David, As far as I understand it, there is no way to immediately expunge a deleted VM easily. By design there's a minimum 10 minute window to allow the recovery of a VM once it has been deleted. If you wanted to remove all references from the database and manually remove the associated files on your primary and secondary storage, there's nothing stopping you from doing that, but you'd probably be best to set your expunge.delay and expunge.interval to 600 and let the system do the heavy lifting. Travis On Aug 26, 2013, at 9:35 AM, David Matteson wrote: > Hey everybody, > > Quick question; there is no API call for it, but does anybody know of a way > to force an expunge to run remotely? Ideally on a specific vmid. > > Thanks!
Remote force expunge?
Hey everybody, Quick question; there is no API call for it, but does anybody know of a way to force an expunge to run remotely? Ideally on a specific vmid. Thanks!
