cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9022) We should keep Destroyed volumes for some time
Date Wed, 04 Nov 2015 05:29:27 GMT


ASF GitHub Bot commented on CLOUDSTACK-9022:

Github user koushik-das commented on a diff in the pull request:
    --- Diff: server/src/com/cloud/configuration/ ---
    @@ -672,6 +672,7 @@
                 "The interval (in seconds) to wait before running the storage cleanup thread.",
    +    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 --
    Please use the Configurable interface for configuration parameters instead. Refer to

> We should keep Destroyed volumes for some time
> ----------------------------------------------
>                 Key: CLOUDSTACK-9022
>                 URL:
>             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'
> We need to add the similar configuration for volumes.

This message was sent by Atlassian JIRA

View raw message