[SERVER-48627] increase timeout on batch_write_command_insert.js in sharding passthrough test suites. Created: 05/Jun/20  Updated: 17/Feb/22  Resolved: 17/Feb/22

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Sprint: Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-10, Execution Team 2022-02-21
Participants:
Linked BF Score: 15

 Description   

We have observed a few instances of this test timing out in our CI system on the collection drop in some sharding passthrough suites. In these failures, the test seemed to be slow in replicating the 100,000 delete operations preceding a createIndexes command to the secondaries. The write concern for the collection drop contained a 60 second timeout, which may be insufficient if we need more time to fully replicate the delete operations.



 Comments   
Comment by Eric Milkie [ 26/Oct/20 ]

The linked build failure is not chronic, and this fix would only change the test not to fail, so I am tabling it back to the backlog for now.

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