Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 30 Nov 2015 20:48:10 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12910030.1446566607000.224432.1448916490953@Atlassian.JIRA>
In-Reply-To: <JIRA.12910030.1446566607000@Atlassian.JIRA>
References: <JIRA.12910030.1446566607000@Atlassian.JIRA>
 <JIRA.12910030.1446566607784@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9022) We should keep Destroyed
 volumes for some time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032430#comment-15032430 ] 

ASF GitHub Bot commented on CLOUDSTACK-9022:
--------------------------------------------

Github user remibergsma commented on the pull request:

    https://github.com/apache/cloudstack/pull/1144#issuecomment-160756847
  
    @ustcweizhou This is a mistake I guess, PR against the wrong branch?


> 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)