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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 2.2.0
    • Querying, Replication, Sharding
    • None
    • ALL

    Description

      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

      Attachments

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

        Activity

          People

            randolph@mongodb.com Randolph Tan
            bwaldvogel Benedikt Waldvogel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: