using RCAR option un-pins secondaries from client connections

XMLWordPrintableJSON

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

      ReleaseConnectionsAfterResponse changes the way in which queries are pinned to secondaries - under load slaveOk queries to secondaries should still have even distribution, but the previous behavior of talking to the same secondary if the same connection was used (except on secondary failure) is no longer enforced.

      In 2.6 RCAR is hardcoded to "on" - we re-use connections between requests.

            Assignee:
            Daniel Pasette (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: