[SERVER-33219] Add a backpressure mechanism to the CRUD client in backup_restore*.js tests Created: 09/Feb/18 Updated: 29/Oct/23 Resolved: 09/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.3, 3.7.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||
| Sprint: | TIG 2018-02-26 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
There appears to have been a significant performance change in WiredTiger from 6554a50 on the SSL Windows 2008R2 builder. It has inadvertently exposed a latent issue in the design of the backup_restore*.js tests, where the CRUD client is able to perform write operations quickly enough that it causes both the secondary taken offline for the backup and the secondary that remains online to fall off the primary's oplog. We should have the CRUD client periodically use a write concern of w=3 to avoid either of the secondaries from becoming too far behind. |
| Comments |
| Comment by Githook User [ 11/Feb/18 ] |
|
Author: {'email': 'max.hirschhorn@mongodb.com', 'name': 'Max Hirschhorn', 'username': 'visemet'}Message: Also fixes the FSM client by changing the concurrency suite to handle (cherry picked from commit fdc23cf6a586a607299ec8a880574e95071e8f39) |
| Comment by Githook User [ 09/Feb/18 ] |
|
Author: {'email': 'max.hirschhorn@mongodb.com', 'name': 'Max Hirschhorn', 'username': 'visemet'}Message: Also fixes the FSM client by changing the concurrency suite to handle |