RGW: Pass and check destination zone trace when fetching object#51715
RGW: Pass and check destination zone trace when fetching object#51715
Conversation
d8c4255 to
ca2bdeb
Compare
ca2bdeb to
201d7e5
Compare
Fixes: https://tracker.ceph.com/issues/58911 Signed-off-by: Alex Wojno <awojno@bloomberg.net>
201d7e5 to
e70fcf9
Compare
|
jenkins test api |
|
jenkins test make check |
|
@awojno-bloomberg looks like all of the required checks have passed 👍 |
sorry still testing, the inconsistent state between zones keeps occuring with this PR on one test setup:
|
mkogan1
left a comment
There was a problem hiding this comment.

updating following more testing, that the rados df stats mismatch is an intermittent temporary rados stats artifact which in above screenshot case corrected itself after 3 hours.
switched to radosgw-admin bucket list ... methodology for object count validation and result are immediate, consistent and correct.
LGTM



The proposed fix for a race condition in multisite during full sync involving deletes. A custom header was added passing the destination zone's trace string and is then checked against the object's replication trace. If there is a match, a 304 response is returned which will prevent full sync from overwriting a deleted object. Please see the tracker for more details.
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows