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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.1, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v4.4
    • Execution Team 2020-08-10, Execution Team 2020-08-24
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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. 

              Assignee:
              Samyukta Lanka
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: