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

Explicitly detect invalid gle reuse when using 'releaseConnectionsAfterResponse' mode

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Sharding
    • None
    • Fully Compatible

    Description

      If a application disobeys the always-gle-after-write requirements for the 'releaseConnnectionsAfterResponse' mode, we may not explicitly detect the failure but instead potentially return bad data from potentially another connection.

      Potential fix - method in ClientConnections::areAllAvailable( const vector<string> gleHosts ) and logic block in ClientInfo::getLastError() which throws a "incorrect use of gle in 'release connections after response' mode" error.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              greg_10gen Greg Studer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: