Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-633

Define how multiple phases should be handled in SDAM spec runner

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: SDAM
    • Labels:
      None
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      RUBY-2051 Fixed 2.12.0.rc0
      CSHARP-2883 Fixed 2.12.0
      GODRIVER-1447 Won't Do
      PHPC-1518 Won't Fix
      MOTOR-483 Works as Designed
      CXX-1897 Backlog
      NODE-2396 Won't Do
      PYTHON-2088 Fixed 3.11
      JAVA-3561 Fixed 4.0.0
      CDRIVER-3469 Backlog
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion RUBY-2051 Fixed 2.12.0.rc0 CSHARP-2883 Fixed 2.12.0 GODRIVER-1447 Won't Do PHPC-1518 Won't Fix MOTOR-483 Works as Designed CXX-1897 Backlog NODE-2396 Won't Do PYTHON-2088 Fixed 3.11 JAVA-3561 Fixed 4.0.0 CDRIVER-3469 Backlog

      Currently, there are tests for SDAM state transitions ("sdam") and some of the events generated by SDAM flow ("sdam monitoring"), but there are areas not covered by the existing monitoring tests, specifically:

      • server removal/server close events
      • some situations when the first response is not from primary
      • multiple servers responding

      The existing "sdam" tests cover topology outcomes in most of these cases, but those tests do not specify the order in which events should be published (or event contents, but this is a minor point).

      https://jira.mongodb.org/browse/SPEC-1280 proposes to add a number of "sdam monitoring" tests to formalize the order of sdam events being published in various situations.

      In order for the new tests to be possible, a change in spec runner is necessary which is to perform assertions on events generated during cluster/topology construction prior to any responses being received from any of the servers.

      This ticket covers the spec runner change - specifically, defining how SDAM spec runner should be implemented with respect to events in multiple phases.

            Assignee:
            Unassigned Unassigned
            Reporter:
            oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: