Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E913310B31 for ; Thu, 6 Jun 2013 01:47:34 +0000 (UTC) Received: (qmail 41743 invoked by uid 500); 6 Jun 2013 01:47:34 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 41707 invoked by uid 500); 6 Jun 2013 01:47:34 -0000 Mailing-List: contact dev-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 dev@cloudstack.apache.org Received: (qmail 41699 invoked by uid 99); 6 Jun 2013 01:47:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jun 2013 01:47:34 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mike.tutkowski@solidfire.com designates 209.85.219.46 as permitted sender) Received: from [209.85.219.46] (HELO mail-oa0-f46.google.com) (209.85.219.46) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jun 2013 01:47:30 +0000 Received: by mail-oa0-f46.google.com with SMTP id h2so1733031oag.5 for ; Wed, 05 Jun 2013 18:47:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=95oO/bydk4xladMaEb21OfWClBRwwsQXZQzXUp3I9n4=; b=jkS7NQec7LgOZHKUlXiZ/3h/fGPOdg/ADiMbIti4oXsrat0zg8H/8M7aNU9hWbC/F0 AGu+ROU39qtzdeebLfr11Qn0oJ7AbeM2m0H0aqgr1pMg2aAnqiXRefXTTfSzxoVcY9SZ NJqS+XpHbToW7vnkIjHGhsx2mKf4IG1e2zm7Q+Tl1nRWftb5Und/c6wfUx0TGPn9FXVs 2kIf7sMEjL3qSoixp8SFeWO7u79gjzkGmtphoxpZZ5soiYJkeqXn9DUW3RGqQwIqqsWF g4jTCYBe4xdjc12CwjArvSCt1w77Vn+uZ6sr9mdBIzNeLPRAlv3z9N7r+ERusB3S+FM/ Ul+g== MIME-Version: 1.0 X-Received: by 10.60.131.143 with SMTP id om15mr8634381oeb.19.1370483229605; Wed, 05 Jun 2013 18:47:09 -0700 (PDT) Received: by 10.182.10.66 with HTTP; Wed, 5 Jun 2013 18:47:09 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Jun 2013 19:47:09 -0600 Message-ID: Subject: Re: deleteVolume is sync From: Mike Tutkowski To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=047d7b4179b312479704de727ec0 X-Gm-Message-State: ALoCoQka+fJju+KGq34nSxb3IfZNGSeZQbSCmSzlY6BCnzpACpYQbXbGPUYPMxKDZIl8noGWhxLr X-Virus-Checked: Checked by ClamAV on apache.org --047d7b4179b312479704de727ec0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hey Marcus, To me, it seems like it should be async, as well. As far as I know (at least in pre 4.2), unless you are deleting a volume that has never been attached to a VM, the CS MS would have to have the hypervisor perform some operation upon the deletion of a CloudStack volume...and that could take a bit of time. On Wed, Jun 5, 2013 at 7:24 PM, Marcus Sorensen wrote= : > Oh, I should add that I traced it through the system, and it actually > sends a DeleteVolumeCommand to the agent. That has to finish before > the sync call completes. > > This is on 4.1, if it changes significantly with the storage refactor, > that's fine, but I'd like to know if there was a reason for it in case > we want to make it async for us. > > On Wed, Jun 5, 2013 at 7:21 PM, Marcus Sorensen > wrote: > > Just wondering why deleteVolume is a sync call. It doesn't seem to > > adhere to the 'mark it removed, let a worker expunge it later after X > > seconds' paradigm. I only noticed this when a storage system was > > taking a bit to do the work and thus blocking the API call. > --=20 *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *=99* --047d7b4179b312479704de727ec0--