Secondaries that perform (foreground) index builds should not be considered for reads with secondaryPreferred

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a secondary builds an index, it is currently built in the foreground. SecondaryPreferred will still consider this node to be healthy, however the read blocks until the index is complete.

      This should be changed so that this node is not considered a valid target for a secondaryPreferred reads anymore until the index build is complete.

            Assignee:
            Unassigned
            Reporter:
            Thomas Rueckstiess (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: