cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Kudryavtsev (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-10188) Resource Accounting for primary storage is Broken
Date Fri, 15 Dec 2017 05:42:00 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ivan Kudryavtsev updated CLOUDSTACK-10188:
------------------------------------------
    Description: 
During storage expunge domain resource statistics for primary storage space is not updated.
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 blocker.

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


> 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.10.0.0
>            Reporter: Ivan Kudryavtsev
>            Priority: Blocker
>
> During storage expunge domain resource statistics for primary storage space is not updated.
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 blocker.



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

Mime
View raw message