cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sadhu suresh (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8151) Global config and periodic thread to cleanup cloud_usage table
Date Tue, 13 Jan 2015 16:23:34 GMT


sadhu suresh commented on CLOUDSTACK-8151:

thanks  for taking the initiative and my suggestion is 
before removing the records from db ,its better to archive the records in local/shared storage
in zipped  format. so that it might be useful for customer in  future, like  if he/her wants
to check his archived records for auditing  or some other purpose. I think it might increase
the complexity  and  not sure is it ok implement in that way ,please share  your thoughts.


> Global config and periodic thread to cleanup cloud_usage table
> --------------------------------------------------------------
>                 Key: CLOUDSTACK-8151
>                 URL:
>             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:
> 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

View raw message