[SERVER-31567] reduce number of threads and iterations in drop_collection.js to 5 threads, 5 iterations Created: 13/Oct/17  Updated: 30/Oct/23  Resolved: 16/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.0-rc0
Fix Version/s: 3.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-35226 now that createCollection and createD... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-10-23
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 16/Oct/17 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: SERVER-31567 reduce number of threads and iterations in drop_collection.js to 5 threads, 5 iterations
Branch: master
https://github.com/mongodb/mongo/commit/b5014cc09b5e63aed2c3db64d860ecde8265c1af

Comment by Esha Maharishi (Inactive) [ 13/Oct/17 ]

max.hirschhorn we probably could. The other test that had this issue, queryoptimizer3.js, only has two threads, but it does hundreds of drops, as opposed to drop_collectionl.js, which has 10 iterations.

What number of threads/iterations do you think we should set? I can run a patch with --repeat with that and send it to you for cr.

Comment by Max Hirschhorn [ 13/Oct/17 ]

esha.maharishi, as an alternative could we reduce the number of threads or iterations of the drop_collection.js FSM workload? I don't think we should give up all testing of the multiple clients concurrently doing a create followed by a drop in a sharded cluster.

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