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

Tagged Secondary Preffered not working as expected - Reads always happening at Primary

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.4.5
    • Fix Version/s: None
    • Component/s: Replication, Sharding
    • Labels:
    • Environment:
      Running on RHEL , Java driver 2.11.2
    • Operating System:
      Linux
    • Steps To Reproduce:
      Hide

      Our test env is a mongos router with 2 shards - 3 mongod's and one arbiter per shard and

      Query generated from Java App . using 2.11.2 driver using tagged secondary preffered mode

      Show
      Our test env is a mongos router with 2 shards - 3 mongod's and one arbiter per shard and Query generated from Java App . using 2.11.2 driver using tagged secondary preffered mode

      Description

      During testing we found that setting read Preference to "secondaryPreferred" always fetched records from primary even if the tag was invalid . But the online documentation suggests an error should be thrown " http://docs.mongodb.org/manual/reference/read-preference/#secondaryPreferred " . This leads me to believe Mongos/Java Driver is not respecting tags or behaving otherwise and always reading from primary . Since our actual deployment is large and geographically we need multiple secondaries

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: