summaryrefslogtreecommitdiff
path: root/swift/common/middleware/catch_errors.py
diff options
context:
space:
mode:
authorgholt <z-launchpad@brim.net>2013-03-04 08:52:24 +0000
committergholt <z-launchpad@brim.net>2013-03-04 08:52:24 +0000
commite064ba1915533d97bea827a9d3876169e5882304 (patch)
treed0ddea63822e69f1f6fa94e0fa43718fb5e677bd /swift/common/middleware/catch_errors.py
parent457ff9672dc03b3ea4e46d429747b45edd133836 (diff)
downloadswift-e064ba1915533d97bea827a9d3876169e5882304.tar.gz
Updated get_more_nodes algorithm
The handoff nodes will try to be in zones other than the primary zones, will take into account the device weights, and will usually keep the same sequences of handoffs even with ring changes. On a real ring test the old get_more_nodes placed data mostly evenly across zones, which is a problem for differently weighted zones. But the real problem was that the extra partitions given to each device was 0% to 0.77% with only 46.05% of the candidate devices getting anything. Some of the devices increased in effective weight over 50% in the test. The new get_more_nodes placed closer to what the zone weights were and the extra partitions given to each device was 0% to 0.24% with 90.58% of the candidate devices getting something. The worst off device only increased in effective weight by 10.71%. Change-Id: Iffb133a22db69074acaa2b90854cbfa92e4c2b9e
Diffstat (limited to 'swift/common/middleware/catch_errors.py')
0 files changed, 0 insertions, 0 deletions