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

Test that LoadBalanced connection handshake uses OP_MSG

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Minor - P4 Minor - P4
    • None
    • Handshake
    • None
    • Not Needed
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      GODRIVER-3054 Fixed 2.0.0, 1.13.1
      $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 GODRIVER-3054 Fixed 2.0.0, 1.13.1

    Description

      Summary

      Create a handshake prose test to ensure that the opcode used for a load balanced handshake is OP_MSG, per the specifications:

      https://github.com/mongodb/specifications/blob/master/source/load-balancers/load-balancers.rst#connection-establishment

      https://github.com/mongodb/specifications/blob/master/source/mongodb-handshake/handshake.rst#connection-handshake

      Motivation

      The Go Driver has always incorrectly used OP_QUERY for load-balanced connection handshakes. The Drivers team should test for this case.

      Who is the affected end user?

      Affected end user is anyone connecting to the Atlas proxy (Serverless)

      How does this affect the end user?

      Confusing log messages shown

      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?

      Yes

      Acceptance Criteria

      Extend the handshake prose test to include:

      (1) If the server is load balanced, then ensure that the handshake uses the OP_MSG opcode
      (2) If not, ensure the handshake uses OP_QUERY

      Attachments

        Activity

          People

            Unassigned Unassigned
            preston.vasquez@mongodb.com Preston Vasquez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: