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

SDAM unit test sharded/too_new needs to defined wireVersions for host b

XMLWordPrintableJSON

    • Needed
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-4727 Blocked
      CXX-2757 Blocked
      CSHARP-4798 Blocked
      GODRIVER-2993 Blocked
      JAVA-5168 Blocked
      NODE-5645 Blocked
      MOTOR-1191 Duplicate
      PYTHON-3967 Blocked
      PHPLIB-1242 Blocked
      RUBY-3330 Blocked
      RUST-1766 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-4727 Blocked CXX-2757 Blocked CSHARP-4798 Blocked GODRIVER-2993 Blocked JAVA-5168 Blocked NODE-5645 Blocked MOTOR-1191 Duplicate PYTHON-3967 Blocked PHPLIB-1242 Blocked RUBY-3330 Blocked RUST-1766 Blocked

      Summary

      What is the problem or use case, what are we trying to achieve?

      SDAM unit test sharded/too_new needs to defined wireVersions for host b. Host b omits a wire version which causes an incompatibility error for having too low a wireVersion since drivers now require the wire version to be greater than 6. The test intends to test for host a's wireVersion set to 999, but if a driver does not correctly check for "too new" wire versions their topology will still be marked incompatible by host b's omission.

      Test file here

      Motivation

      Who is the affected end user?

      Who are the stakeholders?

      How does this affect the end user?

      Are they blocked? Are they annoyed? Are they confused?

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

      Main path? Edge case?

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

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      Is this ticket required by a downstream team?

      Needed by e.g. Atlas, Shell, Compass?

      Is this ticket only for tests?

      Does this ticket have any functional impact, or is it just test improvements?

            Assignee:
            Unassigned Unassigned
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Shane Harvey Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: