[SERVER-56820] Use the correct uuid to construct oplog entry in oplog_writes_only_permitted_on_standalone.js Created: 10/May/21 Updated: 29/Oct/23 Resolved: 12/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2021-05-17 | ||||
| Participants: | |||||
| Linked BF Score: | 133 | ||||
| Description |
|
This test construct the update entry using the latest oplog entry as a template. But the latest oplog entry may not belong to "test.coll" and so that uuid could be wrong. In that case, replication recovery would turn the update into a noop and slightly ignore the update on missing document (in the wrong collection). |
| Comments |
| Comment by Githook User [ 12/May/21 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |