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

Don't log "Index build failed" if it continues in the background due to a stepDown

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.1, 4.7.0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-08-10, Execution Team 2020-08-24

      Description

      During a stepdown, the server logs look like this:

      I  INDEX    [conn2] Index build received interrupt signal{"buildUUID":{"uuid":{"$uuid":"35f19a17-f2e6-435d-ab18-97894162f02e"}},"signal":{"code":11602,"codeName":"InterruptedDueToReplStateChange","errmsg":"operation was interrupted"}}
      I  INDEX    [conn2] Index build ignoring interrupt and continuing in background{"buildUUID":{"uuid":{"$uuid":"35f19a17-f2e6-435d-ab18-97894162f02e"}}}
      I  INDEX    [conn2] Index build failed{"buildUUID":{"uuid":{"$uuid":"35f19a17-f2e6-435d-ab18-97894162f02e"}},"ex":{"code":11602,"codeName":"InterruptedDueToReplStateChange","errmsg":"operation was interrupted"}}
      

      These log messages are contradictory because we report the index build as failing immediately after saying it will continue in the background

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              samy.lanka Samyukta Lanka
              Reporter:
              louis.williams Louis Williams
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: