[SERVER-73164] increase maxTimeMS for index build in index_max_time_ms.js Created: 20/Jan/23  Updated: 29/Oct/23  Resolved: 23/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0, 6.0.5

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-45933 2 phase index build running with maxT... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Execution Team 2023-02-06
Participants:
Linked BF Score: 45

 Description   

On slow machines when the index build takes a long time (longer than the maxTimeMS provided with the createIndexes command) for the IndexBuildsCoordinator to start the build on the thread pool, the index build may time out before the test has a chance to check the db.currentOp() output for the presence of the index build.

We should consider increasing the current maxTimeMS value of 10 seconds to accommodate slow machines.



 Comments   
Comment by Githook User [ 24/Jan/23 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-73164 increase maxTimeMS in index_max_time_ms.js

(cherry picked from commit 3ba868bd5c52de01872fa8d9ee128bb13e18c0f7)
Branch: v6.0
https://github.com/mongodb/mongo/commit/fb1924c6039cfc97647bcf53c387d0491ffae79f

Comment by Githook User [ 20/Jan/23 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-73164 increase maxTimeMS in index_max_time_ms.js
Branch: master
https://github.com/mongodb/mongo/commit/3ba868bd5c52de01872fa8d9ee128bb13e18c0f7

Comment by Benety Goh [ 20/Jan/23 ]

We added this test in SERVER-45933.

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