Index Rebuilder may not always run at startup on a secondary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.3
    • Affects Version/s: 2.5.1
    • Component/s: Replication
    • None
    • Environment:
    • None
    • None
    • None
    • None
    • None
    • None

      It's possible, due to timing, that IndexRebuilder doesn't get going until we've already established that we're a replicaset but not a primary. We need to ensure that nonprimaryness does not inhibit Index Rebuilding

              Assignee:
              Matt Dannenberg (Inactive)
              Reporter:
              Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: