[SERVER-19653] Reduce disk writes in rename_collection_dbname_chain.js FSM workload Created: 29/Jul/15  Updated: 09/Oct/15  Resolved: 29/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
related to SERVER-19664 Reduce disk writes in drop_database.j... Closed
related to SERVER-20842 Reduce test iterations in rename_capp... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 7 08/10/15
Participants:
Linked BF Score: 0

 Description   

In the concurrency suite, the rename_collection_dbname_chain.js FSM workload repeatedly renames collections across databases. With mmapv1, these renames lead to the writing of > 15GB worth of cumulative data during the workload's lifetime.

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 [ 29/Jul/15 ]

Author:

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

Message: SERVER-19653 Reduce test iterations in rename_collection_dbname_chain.js

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/f1bdf1bb55f93c63297f36ef22ed40d6d84872c9

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