Queries fail if no primary server available (primaryPreferred read preference)

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.2.0
    • Component/s: Querying, Replication, Sharding
    • None
    • Environment:
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Due to a crash, bother arbiters and both primary servers fail. Only the two secondary servers are alive but stay in state 'SECONDARY'.

      Querying with the new 'primaryPreferred' read preference should still be possible.
      However, a query using a new connection on the mongo router always fails:

      socket exception [CONNECT_ERROR] for rs1/mongo1:27017,mongo2:27017

        1. PrimaryPreferredTest.java
          1.0 kB
          Benedikt Waldvogel
        2. client.log
          0.6 kB
          Benedikt Waldvogel
        3. mongos.log
          11 kB
          Benedikt Waldvogel

              Assignee:
              Randolph Tan
              Reporter:
              Benedikt Waldvogel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: