[
https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989043#comment-14989043
]
ASF GitHub Bot commented on CLOUDSTACK-9022:
--------------------------------------------
Github user ustcweizhou commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1029#discussion_r43848708
--- Diff: server/src/com/cloud/configuration/Config.java ---
@@ -672,6 +672,7 @@
"86400",
"The interval (in seconds) to wait before running the storage
cleanup thread.",
null),
+ StorageCleanupDelay("Advanced", StorageManager.class, Integer.class,
"storage.cleanup.delay", "86400", "Determines how long (in seconds) to wait
before actually expunging destroyed volumes. The default value = the default
value of storage.cleanup.interval.", null),
--- End diff --
To make the configuration more readable, I will move all the
storage-cleanup related configurations to Configurable interface.
> 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)
