Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-77311

Add a new log message when a secondary node is skipping a two-phase index build with a subset of indexes built

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 4.4.27, 7.0.5, 6.0.13, 5.0.24
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • v7.0, v6.3, v6.0, v5.0, v4.4
    • Execution EMEA Team 2023-07-10, Execution EMEA Team 2023-07-24

      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.

            yujin.kang@mongodb.com Yujin Kang Park
            yujin.kang@mongodb.com Yujin Kang Park
            0 Vote for this issue
            4 Start watching this issue