[SERVER-46943] Correct Idempotency concerns section of initial sync in architecture guide Created: 18/Mar/20  Updated: 29/Oct/23  Resolved: 27/Apr/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc4, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Repl 2020-05-04
Participants:

 Description   

The architecture guide mentions

If known problematic operations such as renameCollection are received, where we cannot assume a drop will come and fix them, we abort and retry initial sync.

This is no longer the case for renameCollection; as of 4.4. I do not think there are any such operations – all idempotency issues are resolved by the time the endTimestamp is reached.



 Comments   
Comment by Githook User [ 30/Apr/20 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}

Message: SERVER-46943 Correct Idempotency concerns section of initial sync in architecture guide

(cherry picked from commit d140082164a67ebc5eb935aa7982b208f18ea274)
Branch: v4.4
https://github.com/mongodb/mongo/commit/825dec9a327ea501fe12d46370b82556152e9cc7

Comment by Githook User [ 27/Apr/20 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}

Message: SERVER-46943 Correct Idempotency concerns section of initial sync in architecture guide
Branch: master
https://github.com/mongodb/mongo/commit/d140082164a67ebc5eb935aa7982b208f18ea274

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