[SERVER-77311] Add a new log message when a secondary node is skipping a two-phase index build with a subset of indexes built Created: 19/May/23  Updated: 20/Nov/23  Resolved: 20/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 4.4.27, 7.0.5, 6.0.13, 5.0.24

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

Issue Links:
Backports
Depends
Related
related to SERVER-71768 Have secondary nodes vote for the ind... Closed
related to SERVER-71769 Add a new log message when a secondar... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.3, v6.0, v5.0, v4.4
Sprint: Execution EMEA Team 2023-07-10, Execution EMEA Team 2023-07-24
Participants:

 Description   

Similar to SERVER-71769, but we should also detect the case were a subset of the indexes is ready. This means it is possible the primary commits the build, while the secondary has skipped it. The secondary would only have a subset of the indexes the primary has. The user should be warned to manually build the remaining indexes on that secondary.

It is also possible that a node which skipped the index build becomes primary, and the index build is never able to commit despite the commit quorum although it may exist in some (or all) secondaries. We should warn against this too.



 Comments   
Comment by Githook User [ 15/Nov/23 ]

Author:

{'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'}

Message: SERVER-77311 Improve log message when secondary skips index build
Branch: v4.4
https://github.com/mongodb/mongo/commit/82cac0ee93191c84c5ca11c59f3d9cb746a1ab2b

Comment by Githook User [ 14/Nov/23 ]

Author:

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

Message: SERVER-77311 Improve log message when secondary skips index build

(cherry picked from commit 673731c4d4b7726eb4d0a0ec22012dd164fa29d1)
Branch: v6.0
https://github.com/mongodb/mongo/commit/cbf294cf522c4304f92e00855b2533898dc01abe

Comment by Githook User [ 14/Nov/23 ]

Author:

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

Message: SERVER-77311 Improve log message when secondary skips index build

(cherry picked from commit 673731c4d4b7726eb4d0a0ec22012dd164fa29d1)
Branch: v5.0
https://github.com/mongodb/mongo/commit/7c4664229f984f9b0b53523a31adb009233fcae5

Comment by Githook User [ 13/Nov/23 ]

Author:

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

Message: SERVER-77311 Improve log message when secondary skips index build

(cherry picked from commit 673731c4d4b7726eb4d0a0ec22012dd164fa29d1)
Branch: v7.0
https://github.com/mongodb/mongo/commit/30356fcf053ea70f8ac6e947ca7c6ea066b3f130

Comment by Githook User [ 20/Jul/23 ]

Author:

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

Message: SERVER-77311 Improve log message when secondary skips index build
Branch: master
https://github.com/mongodb/mongo/commit/673731c4d4b7726eb4d0a0ec22012dd164fa29d1

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