support proxying of tagging requests in replication #18649
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
Motivation and Context
Intended for active-active replication setup with peers under a GLB - where upload goes to one site and tagging request is received on this object on a peer before replication has a chance to complete.
How to test this PR?
site replication setup for A <-> B
upload a very large file on A, and send tagging request to B before replication completes on B.
Note: tag replication will be proxied to A, the
tag set
request on B will return 200 as Return code with an extra headerX-Minio-Tagging-Proxied
to indicate tagging was proxied to peer.In case there are more than one replication targets - proxying will return 200 OK, even if one tag operation succeeded.
Types of changes
Checklist:
commit-id
orPR #
here)