Write-affinity aware object deletion

Code Issues Proposed changes

When deleting objects in multi-region swift delpoyment with write
affinity configured, users always get 404 when deleting object before
it's replcated to approriate nodes.
This patch adds a config item 'write_affinity_handoff_delete_count' so
that operator could define how many local handoff nodes should swift
send request to get more candidates for the final response, or by
default just leave it to swift to calculate the appropriate number.
Change-Id: Ic4ef82e4fc1a91c85bdbc6bf41705a76f16d1341
Closes-Bug: #1503161

This commit is contained in:

Lingxian Kong

2017年06月02日 15:44:52 +12:00

parent 2d18ecdf4b

commit 831eb6e3ce

8 changed files with 471 additions and 230 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

15
etc/proxy-server.conf-sample

View File

@@ -236,6 +236,20 @@ use = egg:swift#proxy

# This option may be overridden in a per-policy configuration section.

# write_affinity_node_count = 2 * replicas

#

# The number of local (as governed by the write_affinity setting) handoff nodes

# to attempt to contact on deletion, in addition to primary nodes.

#

# Example: in geographically distributed deployment of 2 regions, If

# replicas=3, sometimes there may be 1 primary node and 2 local handoff nodes

# in one region holding the object after uploading but before object replicated

# to the appropriate locations in other regions. In this case, include these

# handoff nodes to send request when deleting object could help make correct

# decision for the response. The default value 'auto' means Swift will

# calculate the number automatically, the default value is

# (replicas - len(local_primary_nodes)). This option may be overridden in a

# per-policy configuration section.

# write_affinity_handoff_delete_count = auto

#

# These are the headers whose values will only be shown to swift_owners. The

# exact definition of a swift_owner is up to the auth system in use, but

# usually indicates administrative responsibilities.

@@ -264,6 +278,7 @@ use = egg:swift#proxy

# read_affinity =

# write_affinity =

# write_affinity_node_count =

# write_affinity_handoff_delete_count =

[filter:tempauth]

use = egg:swift#tempauth

Write-affinity aware object deletion

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

15
etc/proxy-server.conf-sample

View File