SlaveOk won't work after slave had a network exception

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.2.4
    • Component/s: Sharding
    • None
    • Environment:
      Linux
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If network exception occurs when mongos read response from secondary, Mongos will call function <isntSecondary> . Mongos will perhaps choose PRIMARY for query, and this decision will be keeped in this woker thread's lifetime, SlaveOk won't work.

            Assignee:
            Unassigned
            Reporter:
            Jack Chan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: