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

Backport failCommand failPoint to 3.6

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Internal Code
    • Labels:
      None

      Description

      In the design for the retryable reads we decided that drivers should also support retryable reads against 3.6 and 4.0 server in addition to 4.2. However, the driver test suite for retryable reads heavily relies on the failCommand fail point, which doesn't exist in 3.6.

      If we don't backport the fail point then retryable reads will be largely untested against a 3.6 server but I don't think this is necessarily a blocker. Retrying is a driver feature and does not depend on server behavior so a driver that works on 4.0 and 4.2 should also work on 3.6. Additionally, we have another driver project that will test retryable reads/writes and transactions against real failover scenarios which should add the lacking test coverage on 3.6.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: