[SERVER-53838] Prevent secondary from falling behind in resharding_oplog_sync_agg_assert_min_oplog.js Created: 15/Jan/21 Updated: 29/Oct/23 Resolved: 26/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0-rc1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Sharding-NYC, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.9
|
||||||||
| Sprint: | Sharding 2021-03-22, Sharding 2021-04-05 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 39 | ||||||||
| Description |
|
The resharding_oplog_sync_agg_assert_min_oplog.js test intentionally uses a small oplog size (1MB) to force oplog truncation to occur without needing to insert a large amount of data. The implicit of w=1 write concern allows the replica set secondary member to fall behind and be unable to catch up from the primary as a sync source. However, it isn't necessary when asserting properties of the $_requestReshardingResumeToken option to the aggregate command to even have a replica set secondary member. |
| Comments |
| Comment by Githook User [ 27/Apr/21 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit 683271cf3052b850a9d98c122f83834f6eb4849e) |
| Comment by Githook User [ 25/Mar/21 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: |