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 3CABB183A5 for ; Mon, 30 Nov 2015 19:48:11 +0000 (UTC) Received: (qmail 46299 invoked by uid 500); 30 Nov 2015 19:48:11 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 46267 invoked by uid 500); 30 Nov 2015 19:48:11 -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 46255 invoked by uid 500); 30 Nov 2015 19:48:11 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 46252 invoked by uid 99); 30 Nov 2015 19:48:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Nov 2015 19:48:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id ED5BD2C1F61 for ; Mon, 30 Nov 2015 19:48:10 +0000 (UTC) Date: Mon, 30 Nov 2015 19:48:10 +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=15032325#comment-15032325 ] ASF GitHub Bot commented on CLOUDSTACK-9022: -------------------------------------------- GitHub user ustcweizhou opened a pull request: https://github.com/apache/cloudstack/pull/1145 [4.6.1] 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. same to #1029 , for 4.6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ustcweizhou/cloudstack storage-cleanup-delay-4.6 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1145.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 #1145 ---- commit 9077c9a5b47224b2d00978ff67e9af6957ec589b Author: Wei Zhou Date: 2015-11-03T16:04:55Z CLOUDSTACK-9022: keep Destroyed volumes for sometime commit 4ed1e0d5f809d1bb2845b6e076d55eeb1ce3f0f4 Author: Wei Zhou Date: 2015-11-04T08:27:32Z CLOUDSTACK-9022: move storage.cleanup related global configurations to StorageManager ---- > 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)