[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320604#comment-16320604
 ] 

ASF subversion and git services commented on CLOUDSTACK-10188:
--------------------------------------------------------------

Commit 7ca4582a852ae874181188280cc654e8fed6bd65 in cloudstack's branch 
refs/heads/master from Bitworks Software, Ltd
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=7ca4582 ]

CLOUDSTACK-10188 - Resource Accounting for primary storage is Broken when 
Domains are in use (#2362)

During storage expunge domain resource statistics for primary storage space 
resource counter is not updated for domain. This leads to the situation when 
domain resource statistics for primary storage is overfilled (statistics only 
increase but not decrease).

Global scheduled task resourcecount.check.interval > 0 provides a workaround 
but not fixes the problem truly because when accounts inside domains use 
primary_storage allocation/deallocation intensively it leads to service block 
of operation.

NB: Unable to implement marvin tests because it (marvin) places in database 
weird primary storage volume size of 100 when creating VM from template. It 
might be a sign of opening a new issue for that bug.

> Resource Accounting for primary storage is Broken
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-10188
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.9.0, 4.10.0.0, 4.11.0.0
>            Reporter: Ivan Kudryavtsev
>
> During storage expunge domain resource statistics for primary storage space 
> resource counter is not updated for domain. This leads to the situation when 
> domain resource statistics for primary storage is overfilled (statistics only 
> increase but not decrease).
> Global scheduled task resourcecount.check.interval > 0 provides a workaround 
> but not fixes the problem truly because when accounts inside domains use 
> primary_storage allocation/deallocation intensively it leads to service block 
> of operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to