[SERVER-71768] Have secondary nodes vote for the index build commit quorum if the index already exists Created: 01/Dec/22  Updated: 14/Jun/23  Resolved: 24/May/23

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Yujin Kang Park
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-77451 Complete TODO listed in SERVER-71768 Closed
is related to SERVER-71769 Add a new log message when a secondar... Closed
is related to SERVER-77311 Add a new log message when a secondar... Closed
Assigned Teams:
Storage Execution
Sprint: Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03, Execution Team 2023-04-17, Execution Team 2023-05-29
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.

It would be ideal if secondary nodes with the index already existing could participate in voting for the commit quorum to avoid this.



 Comments   
Comment by Githook User [ 14/Jun/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-77451 Cleanup refereces to SERVER-71768
Branch: master
https://github.com/mongodb/mongo/commit/8d5ff0751f1b7a89a3e6e50f96dda43ac14def1c

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