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

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

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.4.5
    • Component/s: Replication, Sharding
    • Environment:
      Running on RHEL , Java driver 2.11.2
    • Linux
    • 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

      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

            Assignee:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Reporter:
            vinod.k Vinod Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: