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

index_stepdown_init.js must handle error messages other than IndexBuildAborted

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2019-10-07
    • 17

      index_stepdown_init.js depends on finding "IndexBuildAborted: Index build aborted: " in the server's error message logging. However, the particular error message that the stepdown interruption produces is not limited to the IndexBuildsCoordinator/MultiIndexBlock code. For example, the error message can be produced by the repl code layer.

      One solution is to just require "Index build failed", which we prepend to all index build failures at the higher level. Otherwise, all possible replication error messages must be handled in the JS test. For example, the test failure prompting this ticket had a NotMaster error; and there may be other possible error messages

      See the linked test failure for specifics.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: