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

Incorrect specification of how nodes are chosen for "nearest" read preference

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      On the page http://docs.mongodb.org/manual/applications/replication/#nearest, it states that

      "If you specify a tag set, the client attempts to find a secondary member that matches the specified tag set and directs reads to a random secondary from among the nearest group."

      This makes it seem that the "nearest" read preference in combination with tag sets only allows reading from secondaries, which is incorrect.

      Additionally, the use of the word "random" is misleading because the choice of node depends on implementation. Recommended is either removing it or replacing with "arbitrary".

      Attachments

        Activity

          People

            epc Ed Costello
            sam.helman@10gen.com sam.helman@10gen.com
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              11 years, 5 weeks ago