Allow failPoints to disable "isMaster" failPoints

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing
    • None
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the `failPoint` helpers are unable to clear an "isMaster" failPoint.

      Fortunately, this currently does not affect the tests.

      In the case of a single mongos, the failpoint should be cleared when when the driver rapidly starts requesting heartbeats when subsequent tests run.

      In the case of multiple mongoses, the other mongos will be selected, and heartbeats will slowly disable the the failpoint on the other mongos.

      rstam's proposal that the failpoint helper seems reasonable: the failpoint helper should hang on to the channel instead of the server, that way it has a dedicated already-opened connection it can use to clear the failpoint.

            Assignee:
            Unassigned
            Reporter:
            Vincent Kam (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: