[SERVER-38543] Limit the number of operations backup_cursor_truncate_after.js writes/checks Created: 11/Dec/18  Updated: 29/Oct/23  Resolved: 05/Feb/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.8

Type: Task Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-02-11
Participants:
Linked BF Score: 3

 Description   

A slow machine might take a long while to open its backup cursor and proceed with the test. During this time, the test will write more data that also gets checked after the backup cursor is open.

Consider:

  • Raising the syncdelay from 1 second to 2 or 3 seconds.
  • Limit the number of documents written and/or prune the writerOpTimes down to a max size.


 Comments   
Comment by Githook User [ 05/Feb/19 ]

Author:

{'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}

Message: SERVER-38543 Limit the number of operations backup_cursor_truncate_after.js writes
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/44bae965c82742319a11ab80f3e6811abf4e2828

Generated at Thu Feb 08 04:49:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.