When an SSYNC connection fails after shipping a fragment, but before
cleaning itself up - it can lead to multiple replicas of the same
fragment index serviceable in the node_iter at the same time. Or
perhaps more likely if a partner nodes win a race to rebuild waiting
on a handoff. In this case, the proxy need not fail to service a GET
just because of extra information. A similar guard was added to the
reconstructor in a related change [1].
This underlying bug is acctually fixed by the related change [2], this
probetest is just encoding the failure to help with future maintenance.
Reviewed: https:/ /review. openstack. org/371771 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=116462d8a5a 45ec876403234cf 83b96dfad58ddd
Committed: https:/
Submitter: Jenkins
Branch: master
commit 116462d8a5a45ec 876403234cf83b9 6dfad58ddd
Author: Clay Gerrard <email address hidden>
Date: Fri Sep 16 11:58:46 2016 -0700
Add probetest for response with duplicate frags
When an SSYNC connection fails after shipping a fragment, but before
cleaning itself up - it can lead to multiple replicas of the same
fragment index serviceable in the node_iter at the same time. Or
perhaps more likely if a partner nodes win a race to rebuild waiting
on a handoff. In this case, the proxy need not fail to service a GET
just because of extra information. A similar guard was added to the
reconstructor in a related change [1].
This underlying bug is acctually fixed by the related change [2], this
probetest is just encoding the failure to help with future maintenance.
1. Related-Change: I91f3d4af52cbc6 6c9f7ce00726f24 7b5462e66f9 2ff5d1a739cbcc5 9637ffe3fc3
2. Related-Change: I2310981fd1c462
Closes-Bug: 1624176
Change-Id: I06fc381a256135 85dd18916d50e7c a2c68d406b6