[SERVER-59122] repeated blocked index build messages in logs Created: 05/Aug/21  Updated: 29/Oct/23  Resolved: 06/Aug/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Bug 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:
Depends
Related
is related to SERVER-42967 Add DiagnosticInfo hooks into Interru... Closed
is related to SERVER-47155 Limit the number of simultaneous inde... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2021-08-09
Participants:
Linked BF Score: 52

 Description   

In SERVER-47155, a createIndex command waits for the number of concurrent index builds to fall below a certain limit before proceeding. The log message "Too many index builds running simultaneously, ..." is used to indicate that the index build is blocked.

Due to the placement of this log message within the predicate provided to conditional variable, this log message may be printed multiple times depending on how often the Interruptible class evaluates the predicate or wakes up from a sleep.

In some cases, we have observed this log message printed as many as four times within the same millisecond before the condition variable starts the second phase of its wait logic.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 06/Aug/21 ]

Author:

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

Message: SERVER-59122 log 'Too many index builds running...' message at most once per index build
Branch: master
https://github.com/mongodb/mongo/commit/bcf237d9a7e319cd9d92cec7702fcc689c18931f

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