[SERVER-49903] Implement ordinary "no move" update rule for resharding's oplog application Created: 25/Jul/20  Updated: 29/Oct/23  Resolved: 14/Dec/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: Janna Golden
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49901 Implement ordinary insert rule for re... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-12-14, Sharding 2020-12-28
Participants:
Story Points: 1

 Comments   
Comment by Githook User [ 14/Dec/20 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-49903 Implement ordinary update rule for resharding's oplog application
Branch: master
https://github.com/mongodb/mongo/commit/dbcd3a4ac399b315a2916dade69caef1839f7df7

Comment by Max Hirschhorn [ 02/Nov/20 ]

SERVER-50120 added support for ordinary insert, ordinary delete, and "no move" ordinary update under the assumption that documents as identified by their _id never move between donor shards. SERVER-49901, SERVER-49902, and SERVER-49903 are instead being used to support these operations when documents either move between donor shards or violate the global _id uniqueness assumption. The work involved is to make the oplog application rules (owning donor shard + _id) aware for how they identify a particular donor to modify.

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