replication: use latest object info for metrics update #17333
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.
When there is a lot of MRF backlog being concurrently processed on the same object version, the previous replication status gathered while queuing the task could get stale because a previous replication attempt already succeeded while this task was waiting its turn.
Use the latest replication metadata from reader as previous status to avoid over counting replicated size.
Description
Motivation and Context
Correctness
How to test this PR?
Types of changes
Checklist:
commit-id
orPR #
here)