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

revisit minOpTime logic in serverSelector

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • 4.3 Desired
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability

      This logic was found to be required for test conformance.

      Currently, the server selector code does the equivalent of the old RSM implementation, which is:

      • if tags are specified and minOpTime is in the readPreference, then try to only select servers that fit this requirement. Call this set S. If |S| == 0 then, ignore minOpTime in the readPref.

      I suspect that, from the client's perspective, this has similar runtime characteristics as just ignoring the minOpTime altogether. We should validate whether this is true, and if so remove this logic.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: