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

ASF GitHub Bot commented on CLOUDSTACK-10188:
---------------------------------------------

rhtyd commented on issue #2362: CLOUDSTACK-10188 - Resource Accounting for 
primary storage is Broken when Domains are in use
URL: https://github.com/apache/cloudstack/pull/2362#issuecomment-355898495
 
 
   @bwsw sure, please fix the conflicts.
   Ideally today we are supposed to freeze the branch to only accept 
critical/blocker fixes until the rc1 is put to vote. I'll start a discussion on 
dev@ to gather consensus. Meanwhile, if you've time/bandwidth do work on it.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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