Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B0D8188D4 for ; Tue, 3 Nov 2015 16:27:28 +0000 (UTC) Received: (qmail 90492 invoked by uid 500); 3 Nov 2015 16:27:28 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 90281 invoked by uid 500); 3 Nov 2015 16:27:28 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 90261 invoked by uid 500); 3 Nov 2015 16:27:27 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 90251 invoked by uid 99); 3 Nov 2015 16:27:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2015 16:27:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CFF392C1F5E for ; Tue, 3 Nov 2015 16:27:27 +0000 (UTC) Date: Tue, 3 Nov 2015 16:27:27 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 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)