[SERVER-71769] Add a new log message when a secondary node is skipping a two-phase index build Created: 01/Dec/22  Updated: 29/Oct/23  Resolved: 09/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-73256 [v4.4] Disable rolling_index_builds_i... Closed
related to SERVER-71768 Have secondary nodes vote for the ind... Closed
is related to SERVER-45828 write js test for rolling index builds Closed
is related to SERVER-77311 Add a new log message when a secondar... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.2, v6.0, v5.0, v4.4
Sprint: Execution Team 2022-12-12
Participants:

 Description   

There have been several occurrences in Atlas where one or more secondary nodes already have an index built that the primary does not have. We think this is due to interrupted rolling index builds. Creating the same index on the primary may result in the index build stalling indefinitely as the secondary nodes with the index will return early and skip voting for the index's commit quorum.

The workaround is to adjust the commit quorum using the setIndexCommitQuorum command.

There's no indication of when this happens, so it would be helpful if we can add a log message when a secondary node is skipping the index build to allow the user to take action or for Atlas to detect this automatically via log ingestion.



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

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-71769 Add a new log message when a secondary node is skipping a two-phase index build

(cherry picked from commit fe2d44ca11588c665d17a164ac2c9aed2c24adfb)
Branch: v4.4
https://github.com/mongodb/mongo/commit/df29113ac3419a3acb4736940a0ac05b779f82fb

Comment by Githook User [ 03/Jan/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-71769 Add a new log message when a secondary node is skipping a two-phase index build

(cherry picked from commit fe2d44ca11588c665d17a164ac2c9aed2c24adfb)
Branch: v6.0
https://github.com/mongodb/mongo/commit/085753442350765a473780bcf11d25ae3f8b0528

Comment by Githook User [ 03/Jan/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-71769 Add a new log message when a secondary node is skipping a two-phase index build

(cherry picked from commit fe2d44ca11588c665d17a164ac2c9aed2c24adfb)
Branch: v5.0
https://github.com/mongodb/mongo/commit/19ba515f41993efea900078e3e8f7eaaf583e121

Comment by Githook User [ 08/Dec/22 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-71769 Add a new log message when a secondary node is skipping a two-phase index build
Branch: master
https://github.com/mongodb/mongo/commit/fe2d44ca11588c665d17a164ac2c9aed2c24adfb

Comment by Gregory Wlodarek [ 01/Dec/22 ]

An alternative to this is SERVER-71768.

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