diff options
author | Prashanth Pai <ppai@redhat.com> | 2017-05-11 19:58:30 +0530 |
---|---|---|
committer | Prashanth Pai <ppai@redhat.com> | 2017-05-15 11:47:26 +0000 |
commit | 8af00bf3fa5aa7cd29a53e5e43ea230c196d10b0 (patch) | |
tree | 05fe08476ea55f54945abb15d47f59f06b030732 /doc/markdown/object-expiration.md | |
parent | b572a2af466d1464f525ea773b005539499cbffa (diff) |
Update quick start guide to point to newton releasenewton
and...
- fix anchor tag breakage
- remove old, incomplete doc files
- fix few whitespace nits
Change-Id: I652ef14b689537e6bfdb20f81390f905e6d692f2
Signed-off-by: Prashanth Pai <ppai@redhat.com>
Reviewed-on: https://review.gluster.org/17257
Diffstat (limited to 'doc/markdown/object-expiration.md')
-rw-r--r-- | doc/markdown/object-expiration.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/markdown/object-expiration.md b/doc/markdown/object-expiration.md index a61818a..e1798bc 100644 --- a/doc/markdown/object-expiration.md +++ b/doc/markdown/object-expiration.md @@ -7,18 +7,21 @@ * [Running object-expirer daemon](#running-daemon) <a name="overview" /> + ## Overview The Object Expiration feature offers **scheduled deletion of objects**. The client would use the *X-Delete-At* or *X-Delete-After* headers during an object PUT or POST and the cluster would automatically quit serving that object at the specified time and would shortly thereafter remove the object from the GlusterFS volume. Expired objects however do appear in container listings until they are deleted by object-expirer daemon. This behaviour is expected: https://bugs.launchpad.net/swift/+bug/1069849 <a name="setup" /> + ## Setup Object expirer uses a seprate account (a GlusterFS volume, for now, until multiple accounts per volume is implemented) named *gsexpiring*. You will have to [create a GlusterFS volume](quick_start_guide.md#gluster-volume-setup) by that name. Object-expirer uses the */etc/swift/object-expirer.conf* configuration file. Make sure that it exists. If not, you can copy it from */etc* directory of gluster-swift source repo. <a name="using" /> + ## Using object expiration **PUT an object with X-Delete-At header using curl** @@ -55,6 +58,7 @@ swift --os-auth-token=AUTH_tk99a39aecc3dd4f80b2b1e801d00df846 --os-storage-url=h where *X-Delete-After* header takes a integer number of seconds, after which the object expires. The proxy server that receives the request will convert this header into an X-Delete-At header using its current time plus the value given. <a name="running-daemon" /> + ## Running object-expirer daemon The object-expirer daemon runs a pass once every X seconds (configurable using *interval* option in config file). For every pass it makes, it queries the *gsexpiring* account for "tracker objects". Based on (timestamp, path) present in name of "tracker objects", object-expirer then deletes the actual object and the corresponding tracker object. |