[SERVER-30438] Turn on OPLOG_REPLAY for the change notification query Created: 31/Jul/17 Updated: 30/Oct/23 Resolved: 30/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2017-08-21, Repl 2017-09-11 |
| Participants: |
| Description |
|
The query flag OPLOG_REPLAY needs to be set when doing change notification queries, or the collection scan will have to search the entire oplog from the beginning whenever doing a change notification. We also need to make sure the query is of the proper form for oplog replay for both initial query and resume; this basically means there must be a timestamp "greater than" or "greater than or equal" term at the top level of the query; the system will invariant() if this is not the case. |
| Comments |
| Comment by Githook User [ 30/Aug/17 ] |
|
Author: {'name': 'Matthew Russotto', 'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com'}Message: |