cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Re: deleteVolume is sync
Date Thu, 06 Jun 2013 01:47:09 GMT
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 <shadowsor@gmail.com> 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 <shadowsor@gmail.com>
> 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.
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message