sureshanaparti commented on code in PR #397:
URL: 
https://github.com/apache/cloudstack-documentation/pull/397#discussion_r1593391508


##########
source/adminguide/tuning.rst:
##########
@@ -143,3 +143,76 @@ Article 
<http://support.citrix.com/article/CTX126531>`_.The article
 refers to XenServer 5.6, but the same information applies to XenServer 6
 
 
+Purging Expunged Resources
+--------------------------
+
+..note::
+  Currently only available for Instances and their linked resources.
+
+Over the time there are chances of piling up of millions of database records
+for the removed or expunged resources. The presence of a lot of useless
+records in the database can also affect the performance of cloud so it is
+needed to purge such entries in a systematic way.
+CloudStack provides the following methods to allow purging of the expunged
+resources and their database records:
+
+Using background task
+~~~~~~~~~~~~~~~~~~~~~
+
+A background task will run at regular intervals. The interval for the task and
+other parameters for it such as resource types, start and end date and batch 
size
+can also be controlled with the help of global settings.
+
+The following new global settings have been introduced which would allow
+configuring background task for purging the expunged resources:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+================================================   ================   
===================================================================
+Global setting                                     Default values     
Description
+================================================   ================   
===================================================================
+expunged.resources.purge.enabled                   false              Whether 
to run a background task to purge the expunged resources.
+expunged.resources.purge.resources                 (empty)            A 
comma-separated list of resource types that will be considered by the 
background task to purge the expunged resources. Currently only VirtualMachine 
is supported. An empty "value will result in considering all resource types for 
purging.
+expunged.resources.purge.interval                  86400              Interval 
(in seconds) for the background task to purge the expunged resources.
+expunged.resources.purge.delay                     300                Initial 
delay (in seconds) to start the background task to purge the expunged resources 
task.
+expunged.resources.purge.batch.size                50                 Batch 
size to be used during expunged resources purging.
+expunged.resources.purge.start.time                (empty)            Start 
time to be used by the background task to purge the expunged resources. Use 
format yyyy-MM-dd or yyyy-MM-dd HH:mm:ss.
+expunged.resources.purge.keep.past.days            30                 The 
number of days in the past from the execution time of the background task to 
purge the expunged resources for which the expunged resources must not be 
purged. To enable purging expunged resource till the execution of the 
background task, set the value to zero.

Review Comment:
   ```suggestion
   expunged.resources.purge.keep.past.days            30                 The 
number of days in the past from the execution time of the background task to 
keep the expunged resources for which the expunged resources must not be 
purged. To enable purging expunged resource till the execution of the 
background task, set the value to zero.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to