Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-7925

Need to make clear nearest calculation not done with secondaryPreferred

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 01112017-cleanup
    • mongodb-2.6, mongodb-3.0, mongodb-3.2
    • manual
    • None

    Description

      I reviewed the v2.6.8 code for selecting the members based on the read preference.

      The nearest calculation is not used when using the "secondaryPreferred" read preference. In other words, the members selected are all secondaries and primaries regardless of ping times. If a secondary cannot be selected, then the primary is selected.

      The nearest calculation is done when using the "secondary" read preference. See code.

      This code has changed since 2.6.8. We should be clear about which read preferences cause the nearest calculation to be done.

      Attachments

        Activity

          People

            Unassigned Unassigned
            steven.hand Steven Hand
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              7 years, 38 weeks, 1 day ago