[SERVER-50326] Restrict sharding in agg_out.js workload to a single thread Created: 14/Aug/20  Updated: 29/Oct/23  Resolved: 31/Aug/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.7.0, 4.2.10, 4.4.2

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: James Wahlin
Resolution: Fixed Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2
Participants:
Linked BF Score: 9

 Description   

agg_out.js involves heavy writes and DDL's, so it can cause secondaries to fail to catch up in replication concurrency tests. When sharding is also involved, multiple concurrent collection sharding invocations can lead to shardCollection command timeout.



 Comments   
Comment by Githook User [ 14/Sep/20 ]

Author:

{'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}

Message: SERVER-50326 Restrict sharding in agg_out.js workload to a single thread

(cherry picked from commit 98d95e18f39540b33c491052901579b71ec430fc)
(cherry picked from commit ea20b8a22518250acaac184f07957bdf6cde2b35)
Branch: v4.2
https://github.com/mongodb/mongo/commit/f815b3e1a078b4d803614afb6b8603ea561505ce

Comment by Githook User [ 11/Sep/20 ]

Author:

{'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}

Message: SERVER-50326 Restrict sharding in agg_out.js workload to a single thread

(cherry picked from commit 98d95e18f39540b33c491052901579b71ec430fc)
Branch: v4.4
https://github.com/mongodb/mongo/commit/ea20b8a22518250acaac184f07957bdf6cde2b35

Comment by Githook User [ 31/Aug/20 ]

Author:

{'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}

Message: SERVER-50326 Restrict sharding in agg_out.js workload to a single thread
Branch: master
https://github.com/mongodb/mongo/commit/98d95e18f39540b33c491052901579b71ec430fc

Generated at Thu Feb 08 05:22:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.