4337b753f5
There are several errors related to the swift replication service. The swift storage charm is not properly restarting the services after configuration changes, the correct object_lockup_timeout value (that per the behaviour observerd in our environments must be greater than object_rsync_timeout) and we also needed to fix the object replicator config file to honor the object-handoffs-first configuration. This patch along with the swift proxy-change should fix the currently known replication problems. Closes-bug: #1903762 Depends-on: I87eb23de94e3f2f5b06d44df1f8bd9d2324456a0 Change-Id: I87eb23de94e3f2f5b06d44df1f8bd9d2324c8470 |
||
---|---|---|
.. | ||
001-baseconfig | ||
050-swift-storage.conf | ||
account-server-replicator.conf | ||
account-server.conf | ||
container-server-replicator.conf | ||
container-server.conf | ||
object-server-replicator.conf | ||
object-server.conf | ||
swift.conf | ||
vaultlocker.conf.j2 |