Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-3197

Non Blocking Secondary Reads with 4.0

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Query Operations
    • Labels:
      None
    • Environment:
      RHEL 7.4 Enterprise MongoDB

      Description

      I have questions about the non-blocking secondary reads with MongoDB 4.0+

      1. We have a primary and 3 secondaries. When we set the read preference as "secondaryPreferred", does the client choose only one secondary amongst the 3 secondaries and direct its reads to that secondary? Or does it load balance across 2ndaries?
      1. I am seeing read requests coming into one secondary even when I leave the read preference as default i.e. Primary. I see the same behavior when I set the read preference as 2ndar preferred. I have attached screenshot of the document metrics and OpCounter stats (from Ops Mgr) when we have the default primary read pref. Does it make sense? Or am I doing something incorrect?

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            satish.anupindi@aexp.com Satish Anupindi
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: