[
https://issues.apache.org/jira/browse/CLOUDSTACK-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275545#comment-14275545
]
Rohit Yadav commented on CLOUDSTACK-8151:
-----------------------------------------
Hi [~sadhu], I thought about this too and shared the idea of providing explicit
cleanup triggered by an API call (that is to say instead of a global conf and a
background cleanup thread, users use an API to trigger cleanup). The API option
beats the purpose to automatically cleanup things but I think could be more
sane than CloudStack automatically removing entries from the tables.
> Global config and periodic thread to cleanup cloud_usage table
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-8151
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8151
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0, 4.6.0
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.6.0
>
>
> The cloud_usage table can be very big and once the raw data is processed we
> can safely remove the rows to reduce database size. There is a KB on this:
> http://support.citrix.com/article/CTX139043
> The aim is to create a global config (delete records older than specified no.
> of days) and an API (if necessary) to trigger cleaning up of old entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
