[SERVER-49908] Update config.localReshardingOperations.recipient.progress_applier document following each batch of resharding's oplog application Created: 25/Jul/20  Updated: 29/Oct/23  Resolved: 21/Oct/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-49900 Update config.localReshardingOperatio... Closed
related to SERVER-50964 Create temporary swappable promise co... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2020-10-19, Sharding 2020-11-02
Participants:

 Description   

Store the largest _id value from the oplog entries applied from that donor shard in the config.localReshardingOperations.recipient.progress_applier document as the <progress {clusterTime, ts}> for that donor shard.

{
    _id: <donor's shard ID>,
    progress: <donor1's progress {clusterTime, ts}>,
}

The largest _id value from the oplog entries applied from that donor shard should be used with {$match: {_id: {$gt: <progress {clusterTime, ts}>}}} to resume.

When the donor shard's final oplog entry marker is applied, the config.localReshardingOperations.recipient.progress_applier document can be updated to store {_id: MaxKey} as an indicator that resuming is no longer necessary.



 Comments   
Comment by Githook User [ 21/Oct/20 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-49908 Update config.localReshardingOperations.recipient document following each batch of resharding's oplog application
Branch: master
https://github.com/mongodb/mongo/commit/306f04029f01d3bfb7bc565fb2139862daa57397

Comment by Max Hirschhorn [ 12/Oct/20 ]

renctan, based on the discussion in https://jira.mongodb.org/browse/SERVER-50964?focusedCommentId=3408918&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3408918, I think we're changing the design (and still need to update the text in this ticket's description) to store progress for resharding's oplog applier in its own document separate from the document in config.localReshardingOperations.recipient.

Generated at Thu Feb 08 05:21:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.