Look into retrying index builds automatically in the primary driven index builds suite

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As a follow-on to discussion here

      We lose test coverage because in a failover scenario, we do not restart index builds when the new node steps up (rather, we abort it with InterruptedDueToReplStateChange).

      If we automatically restart the index build on failover either via a suite override or some other test adjustment, we may be able to re-enable some or all of these tests. 

            Assignee:
            Unassigned
            Reporter:
            Malik Endsley
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: