[
https://issues.apache.org/jira/browse/CLOUDSTACK-8985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971751#comment-14971751
]
ASF GitHub Bot commented on CLOUDSTACK-8985:
--------------------------------------------
Github user mike-tutkowski commented on the pull request:
https://github.com/apache/cloudstack/pull/968#issuecomment-150677439
I have actually not witnessed any issue with concurrent deletions. I've run
tests on that and they passed just fine.
On Friday, October 23, 2015, pdube <[email protected]> wrote:
> @mike-tutkowski <https://github.com/mike-tutkowski> Thanks. That makes
> more sense now. So concurrent deletions would still be a problem?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/cloudstack/pull/968#issuecomment-150675450>.
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: [email protected]
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*
> Deleted volume's removed column not updated
> -------------------------------------------
>
> Key: CLOUDSTACK-8985
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8985
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.6.0
> Environment: All
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Fix For: 4.6.0
>
>
> Note: Relates to managed storage only.
> Due to the fact that a volume does not enter the "Expunged" state until after
> a callback method is invoked (which happens after the plug-in is notified to
> delete the volume in question), the current getUsedBytes implementation (in
> SolidFirePrimaryDataStoreDriver) was assuming the volume just deleted would
> not be included in the used-byte count calculation.
> The fact that the code does try to count this volume in the used-byte count
> calculation leads to an exception being thrown and the removed column not
> being updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
