Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-95548

Take ownership of hello protocol

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • N&O Prioritized List, Networking & Obs 2024-10-28

      The N&O team charter states that we own the hello protocol, but we do not own the integration tests or code for it. We will extract code for the hello framework into separate files owned by N&O to clearly establish ownership.

      Code:
      CmdHello, handleHelloResponse, etc/

      Test:

      1. jstests/noPassthrough/replication/awaitable_hello_metrics.js
      2. jstests/noPassthrough/replication/awaitable_hello.js
      3. jstests/replsets/awaitable_hello_fcv_change.js
      4. jstests/replsets/awaitable_hello_metrics_on_state_change.js
      5. jstests/replsets/awaitable_hello_on_nodes_with_invalid_configs.js
      6. jstests/replsets/awaitable_hello_errors_on_horizon_change.js
      7. jstests/replsets/quiesce_mode.js
      8. jstests/sharding/mongos_quiesce_mode.js

      It would be useful for us to own these tests. Specifically, the noPassthrough/ tests are important to own so that we ensure that we test that gRPC behaves with the protocol/increments metrics appropriately.

            Assignee:
            Unassigned Unassigned
            Reporter:
            erin.mcnulty@mongodb.com Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: