[SERVER-41873] Remove most uses of 'oplogreplay' flag in 4.5 Created: 21/Jun/19 Updated: 29/Oct/23 Resolved: 26/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Xin Hao Zhang (Inactive) | Assignee: | David Storch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2020-03-23, Query 2020-04-06 |
| Participants: |
| Description |
|
The `oplogreplay` flag was deprecated for 4.4 nodes inĀ SERVER-36186 but some code for serialization/deserialization and replication was kept to remain compatible with 4.2 nodes. Uses of `oplogreplay` can now be safely removed for 4.6. `oplogreplay` flag should still be permitted to remain compatible with drivers. |
| Comments |
| Comment by Githook User [ 26/Mar/20 ] |
|
Author: {'email': 'david.storch@mongodb.com', 'name': 'David Storch', 'username': 'dstorch'}Message: Starting in 4.4, this flag is accepted by the server but In order to avoid breaking old drivers, the 'oplogReplay' |
| Comment by Ted Tuckman [ 24/Jun/19 ] |
|
This fix version should be 4.5 desired or required, but that fix version doesn't exist yet. We're using 4.3 Required so we remember to update this later. |