doc: Added radosgw temp remove.

fixes: #3278

Signed-off-by: John Wilkins <john.wilkins@inktank.com>

diff --git a/doc/radosgw/index.rst b/doc/radosgw/index.rst
index feaf53915983c72c73ee500a64ec259f7e425679..dd28676b9a989c8f22ed23e1b779a6a77c5625e0 100644 (file)
--- a/doc/radosgw/index.rst
+++ b/doc/radosgw/index.rst
@@ -38,6 +38,7 @@ one API and retrieve it with the other.
        Manual Install <manual-install>
        Configuration <config>
        Config Reference <config-ref>
+       Purging Temp Data <purge-temp>
        S3 API <s3>
        Swift API <swift/index>
        Admin API <admin/index>

diff --git a/doc/radosgw/purge-temp.rst b/doc/radosgw/purge-temp.rst
new file mode 100644 (file)
index 0000000..91181f4
--- /dev/null
+++ b/doc/radosgw/purge-temp.rst
@@ -0,0 +1,18 @@
+========================
+ Purging Temporary Data
+========================
+
+.. deprecated:: 0.52
+
+When you delete objects (and buckets/containers), the Gateway marks the  data
+for removal, but it is still available to users until it is purged. Since data
+still resides in storage until it is purged, it may take up available storage
+space. To ensure that data marked for deletion isn't taking up a significant
+amount of storage space, you should run the following command periodically:: 
+
+       radosgw-admin temp remove
+
+.. important:: Data marked for deletion may still be read. So consider
+   executing the foregoing command a reasonable interval after data
+   was marked for deletion.
+.. tip:: Consider setting up a ``cron`` job to purge data.
\ No newline at end of file