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

DBClientRS should check that pinned hosts still match read preference

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Incomplete
    • 2.6.0-rc1
    • None
    • Internal Client
    • None
    • ALL

    Description

      Similar to SERVER-12583 which only checked for whether we thought the host was up or down. We should also check that other requirements of the read preference are still acceptable.

      One complication that may need to be considered is what to do if there is now a "better" host that we should use. As an example if we were using PrimaryPreferred and settled for a secondary, should we unpin when a primary becomes available. What about hosts with lower ping times or that match an earlier tag predicate?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: