[SERVER-19664] Reduce disk writes in drop_database.js FSM workload Created: 30/Jul/15  Updated: 19/Sep/15  Resolved: 31/Jul/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.1.6
Fix Version/s: 3.1.7

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Kamran K.
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-19653 Reduce disk writes in rename_collecti... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 7 08/10/15
Participants:

 Description   

This bug is similar to SERVER-19653.

In the concurrency suite, the drop_database.js FSM workload repeatedly creates and drops collections. With mmapv1, these sequences lead to the writing of ~12GB worth of cumulative data during the workload's lifetime, when run against a replica set.

We should reduce the amount of data written to disk to speed up the workload and to prevent failures on Evergreen hosts.



 Comments   
Comment by Githook User [ 31/Jul/15 ]

Author:

{u'username': u'kkmongo', u'name': u'Kamran Khan', u'email': u'kamran.khan@mongodb.com'}

Message: SERVER-19664 Reduce test iterations in drop_database.js FSM workload

The workload writes a lot of data to disk with mmapv1 because of 16MB
.ns and .0 files. This can cause fsm_all_replication.js to time out
on slow test hosts because the disk allocations do not complete within
five minutes.
Branch: master
https://github.com/mongodb/mongo/commit/906c38b606f83034e0c063edbc20581077a9109a

Generated at Thu Feb 08 03:51:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.