[
https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987554#comment-14987554
]
ASF GitHub Bot commented on CLOUDSTACK-9022:
--------------------------------------------
GitHub user ustcweizhou opened a pull request:
https://github.com/apache/cloudstack/pull/1029
CLOUDSTACK-9022: keep Destroyed volumes for sometime
for now, the Destroyed volumes will be expunged in Storage cleanup thread,
no matter when they are destroyed.
In Expunging vm thread, we expunge the Destroyed vms which have been
destroyed at least 'expunge.delay' seconds. We add the similar configuration
for volumes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ustcweizhou/cloudstack storage-cleanup-delay
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1029.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1029
----
commit e411f00fdb49615e45f3e0f3fe709d97734d3db2
Author: Wei Zhou <[email protected]>
Date: 2015-11-03T16:04:55Z
CLOUDSTACK-9022: keep Destroyed volumes for sometime
----
> We should keep Destroyed volumes for some time
> ----------------------------------------------
>
> Key: CLOUDSTACK-9022
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9022
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Wei Zhou
> Assignee: Wei Zhou
>
> for now, the Destroyed volumes will be expunged in Storage cleanup thread, no
> matter when they are destroyed.
> In Expunging vm, we only clean the Destroyed vms which have been destroyed at
> least 'expunge.delay' seconds.
> We need to add the similar configuration for volumes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
