[SERVER-43193] Always disable document validation on secondaries Created: 06/Sep/19 Updated: 29/Oct/23 Resolved: 08/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.16 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 10 | ||||||||||||||||
| Description |
|
This may only be a bug on 3.6 or 3.6 and 4.0. We need to make sure this applies to CRUD ops, and also to CRUD ops in applyOps oplog entries. |
| Comments |
| Comment by Githook User [ 08/Nov/19 ] |
|
Author: {'username': 'judahschvimer', 'email': 'judah.schvimer@10gen.com', 'name': 'Judah Schvimer'}Message: |
| Comment by Judah Schvimer [ 23/Sep/19 ] |
|
3.6 applies every oplog entry one at a time during replication recovery. For normal CRUD ops it does disable document validation, but not for CRUD ops that are part of an applyOps oplog entry. 4.0 and beyond use the OplogApplier in replication recovery which always disables document validation. |
| Comment by Suganthi Mani [ 23/Sep/19 ] |
|
judah.schvimer In the meeting, I mentioned about doing document validation during initial sync. But, then, I noticed that we disable the collection validation for initial sync even if there is an active validator present in collection spec (see |
| Comment by Judah Schvimer [ 06/Sep/19 ] |
|
We tried allowing document validation in |