diff options
| author | Tim Burke <tim.burke@gmail.com> | 2020-06-02 16:14:46 -0700 |
|---|---|---|
| committer | Tim Burke <tburke@nvidia.com> | 2020-11-10 18:22:01 +0000 |
| commit | e78377624ab7d34d2fedc06e907dcb9899d89b4a (patch) | |
| tree | 441bffec17c6028a40fce2c5d03bacc9eec0d366 /doc | |
| parent | f5e03ee973fa12088306809bd00ba26ec1d0ab1b (diff) | |
| download | swift-e78377624ab7d34d2fedc06e907dcb9899d89b4a.tar.gz | |
Add a new URL parameter to allow for async cleanup of SLO segments
Add a new config option to SLO, allow_async_delete, to allow operators
to opt-in to this new behavior. If their expirer queues get out of hand,
they can always turn it back off.
If the option is disabled, handle the delete inline; this matches the
behavior of old Swift.
Only allow an async delete if all segments are in the same container and
none are nested SLOs, that way we only have two auth checks to make.
Have s3api try to use this new mode if the data seems to have been
uploaded via S3 (since it should be safe to assume that the above
criteria are met).
Drive-by: Allow the expirer queue and swift-container-deleter to use
high-precision timestamps.
Change-Id: I0bbe1ccd06776ef3e23438b40d8fb9a7c2de8921
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/saio/swift/proxy-server.conf | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/saio/swift/proxy-server.conf b/doc/saio/swift/proxy-server.conf index 8b64a6c09..57a054087 100644 --- a/doc/saio/swift/proxy-server.conf +++ b/doc/saio/swift/proxy-server.conf @@ -34,6 +34,7 @@ use = egg:swift#dlo [filter:slo] use = egg:swift#slo +allow_async_delete = True [filter:container_sync] use = egg:swift#container_sync |