summaryrefslogtreecommitdiff
path: root/etc
diff options
context:
space:
mode:
authorZuul <zuul@review.opendev.org>2022-01-27 21:37:03 +0000
committerGerrit Code Review <review@openstack.org>2022-01-27 21:37:03 +0000
commit4d480044831fb52a63002f668617b10ecef64558 (patch)
treed24213bdbca41376aa2d9490b18382c2e44429d0 /etc
parentd765eefd295c9194caec5fc428db4591ecbbd979 (diff)
parent8c6ccb5fd41864155a043856ff9240e84999e4bf (diff)
downloadswift-4d480044831fb52a63002f668617b10ecef64558.tar.gz
Merge "proxy: Add a chance to skip memcache when looking for shard ranges"
Diffstat (limited to 'etc')
-rw-r--r--etc/proxy-server.conf-sample9
1 files changed, 9 insertions, 0 deletions
diff --git a/etc/proxy-server.conf-sample b/etc/proxy-server.conf-sample
index de51c7bcc..b89f8e6c4 100644
--- a/etc/proxy-server.conf-sample
+++ b/etc/proxy-server.conf-sample
@@ -144,6 +144,15 @@ use = egg:swift#proxy
# so this value should be set less than recheck_updating_shard_ranges.
# recheck_listing_shard_ranges = 600
#
+# For particularly active containers, having information age out of cache can
+# be quite painful: suddenly thousands of requests per second all miss and
+# have to go to disk. By (rarely) going direct to disk regardless of whether
+# data is present in memcache, we can periodically refresh the data in memcache
+# without causing a thundering herd. Values around 0.0 - 0.1 (i.e., one in
+# every thousand requests skips cache, or fewer) are recommended.
+# container_updating_shard_ranges_skip_cache_pct = 0.0
+# container_listing_shard_ranges_skip_cache_pct = 0.0
+#
# object_chunk_size = 65536
# client_chunk_size = 65536
#