[
https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036596#comment-15036596
]
ASF subversion and git services commented on CLOUDSTACK-9022:
-------------------------------------------------------------
Commit 5b7d935ab0b35bec936785e44023ac0d8552e72b in cloudstack's branch
refs/heads/4.6 from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5b7d935 ]
Merge pull request #1145 from ustcweizhou/storage-cleanup-delay-4.6
[4.6.1] CLOUDSTACK-9022: keep Destroyed volumes for sometimefor 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.
same to #1029 , for 4.6
* pr/1145:
CLOUDSTACK-9022: move storage.cleanup related global configurations to
StorageManager
CLOUDSTACK-9022: keep Destroyed volumes for sometime
This closes #1029
Signed-off-by: Remi Bergsma <[email protected]>
> 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)
