[SERVER-45398] Reduce the amount of logging done in sharded_backup_restore.js Created: 07/Jan/20 Updated: 29/Oct/23 Resolved: 17/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2020-01-27 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The sharded backup restore test uses a syncdelay of one second, causing checkpoints to be taken frequently enough that slow machines will have trouble opening backup cursors. This causes the backup cursors to continually retry to open and fail. During this period, there are continuous inserts occurring, which is causing the logs to become too large to open on Evergreen since it logs every insert done. |
| Comments |
| Comment by Githook User [ 16/Jan/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |