[SERVER-33618] Initial sync should consider applyOps a CrudOpType Created: 02/Mar/18  Updated: 29/Oct/23  Resolved: 05/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.4

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-33509 inconsistent treatment of applyOps du... Closed
is related to SERVER-32913 Parallelize application of applyOps o... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2018-04-09
Participants:
Linked BF Score: 19

 Description   

applyOps entries on secondaries can only have CRUD ops in them, so we should relax NamespaceNotFound Errors on them like we do for CRUD ops.



 Comments   
Comment by Githook User [ 05/Apr/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-33618 initial sync should consider applyOps a CrudOpType
Branch: v3.6
https://github.com/mongodb/mongo/commit/ffe04b5ef2ac3f5ca0061db6071779f329c2e23f

Comment by Benety Goh [ 02/Apr/18 ]

As a consequence of SERVER-33509 and SERVER-32913, which were completed shortly after this ticket was created, the work described here may not be applicable to 3.7 anymore. We may still encounter this issue in versions 3.6 and before.

Comment by Benety Goh [ 02/Mar/18 ]

Sounds good to me.

Comment by Judah Schvimer [ 02/Mar/18 ]

benety.goh, do you see any problem with this?

Generated at Thu Feb 08 04:34:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.