Deprecate expirer options

Code Issues Proposed changes

The following configuration options are deprecated:
 * expiring_objects_container_divisor
 * expiring_objects_account_name
The upstream maintainers are not aware of any clusters where these have
been configured to non-default values.
UpgradeImpact:
Operators are encouraged to remove their "container_divisor" setting and
use the default value of 86400.
If a cluster was deployed with a non-standard "account_name", operators
should remove the option from all configs so they are using a supported
configuration going forward, but will need to deploy stand-alone expirer
processes with legacy expirer config to clean-up old expiration tasks
from the previously configured account name.
Co-Authored-By: Alistair Coles <alistairncoles@gmail.com>
Co-Authored-By: Jianjian Huo <jhuo@nvidia.com>
Change-Id: I5ea9e6dc8b44c8c5f55837debe24dd76be7d6248

This commit is contained in:

Clay Gerrard

2024年10月16日 09:23:12 -05:00

committed by Jianjian Huo

parent ae6300af86

commit b69a2bef45

20 changed files with 672 additions and 193 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
etc/proxy-server.conf-sample

View File

@@ -37,8 +37,6 @@ bind_port = 8080

# cert_file = /etc/swift/proxy.crt

# key_file = /etc/swift/proxy.key

#

# expiring_objects_container_divisor = 86400

# expiring_objects_account_name = expiring_objects

#

# You can specify default log routing here if you want:

# log_name = swift

Deprecate expirer options

2 etc/proxy-server.conf-sample Unescape Escape View File

2
etc/proxy-server.conf-sample

View File