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

Publish TopologyDescriptionChangedEvent on topology close

    XMLWordPrintableJSON

Details

    • Needed
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-4757 Blocked
      CXX-2780 Blocked
      CSHARP-4830 Blocked
      GODRIVER-3035 Blocked
      JAVA-5229 Blocked
      NODE-5723 Blocked
      MOTOR-1205 Blocked
      PYTHON-4021 Blocked
      PHPLIB-1300 Blocked
      RUBY-3344 Blocked
      RUST-1791 Blocked
      $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 CDRIVER-4757 Blocked CXX-2780 Blocked CSHARP-4830 Blocked GODRIVER-3035 Blocked JAVA-5229 Blocked NODE-5723 Blocked MOTOR-1205 Blocked PYTHON-4021 Blocked PHPLIB-1300 Blocked RUBY-3344 Blocked RUST-1791 Blocked

    Description

      Summary

      Currently .NET and Rust drivers (maybe other drivers as well) set topology description to Unknown and emit TopologyDescriptionChangedEvent on closing (before TopologyClosedEvent).
      The SDAM logs tests account for that.

      The question is whether when TopologyClosedEvent if emitted, should the topology be in up to date state, which Unknown state (all servers are removed by then).
      Consider adding this behaviour to SDAM specification for a better topology state management.

      For events consistency across all drivers, it would be useful to clarify the desired behaviour on topology close.

      If decided that TopologyDescriptionChangedEvent should not be published on topology close, SDAM logging tests need to be updated accordingly.

      Motivation

      Who is the affected end user?

      Drivers

      How does this affect the end user?

      No known affect

      How likely is it that this problem or use case will occur?

      Main path

      If the problem does occur, what are the consequences and how severe are they?

      Events consistency among drivers.

      Is this issue urgent?

      No

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      Yes, logging tests

      Acceptance Criteria

      What specific requirements must be met to consider the design phase complete?

      Attachments

        Activity

          People

            warren.james@mongodb.com Warren James
            boris.dogadov@mongodb.com Boris Dogadov
            Shane Harvey Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: