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 <shadow...@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.
