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

Update initial DNS seedlist discovery tests to support dedicated load balancer port

    XMLWordPrintableJSON

Details

    • Needed
    • Hide

      The driver updates required in DRIVERS-1983 break the initial-dns-seedlist-discovery load-balanced tests because those tests still point the driver directly at the mongos instances, requiring that the driver still mocks the service ID. See this comment for more details about the test failures in the Go driver.

      Update those tests and the associated DNS records to point the driver at the load balancer started by run-load-balancer.sh, allowing drivers to stop mocking service ID.

      Here's the ticket for updating the DNS records: https://jira.mongodb.org/browse/BUILD-14668
      Here's a PR for the test changes: https://github.com/mongodb/specifications/pull/1148
      Here's the draft PR testing the spec test changes in the Go driver: https://github.com/mongodb/mongo-go-driver/pull/861

      Show
      The driver updates required in DRIVERS-1983 break the initial-dns-seedlist-discovery load-balanced tests because those tests still point the driver directly at the mongos instances, requiring that the driver still mocks the service ID. See this comment for more details about the test failures in the Go driver. Update those tests and the associated DNS records to point the driver at the load balancer started by run-load-balancer.sh, allowing drivers to stop mocking service ID. Here's the ticket for updating the DNS records: https://jira.mongodb.org/browse/BUILD-14668 Here's a PR for the test changes: https://github.com/mongodb/specifications/pull/1148 Here's the draft PR testing the spec test changes in the Go driver: https://github.com/mongodb/mongo-go-driver/pull/861

    Description

      Summary

      The driver updates required in DRIVERS-1983 break the initial-dns-seedlist-discovery load-balanced tests because those tests still point the driver directly at the mongos instances, requiring that the driver still mocks the service ID. See this comment for more details about the test failures in the Go driver.

      Update those tests and the associated DNS records to point the driver at the load balancer started by run-load-balancer.sh, allowing drivers to stop mocking service ID.

      Here's the ticket for updating the DNS records: https://jira.mongodb.org/browse/BUILD-14668
      Here's a PR for the test changes: https://github.com/mongodb/specifications/pull/1148
      Here's the draft PR testing the spec test changes in the Go driver: https://github.com/mongodb/mongo-go-driver/pull/861

      Motivation

      Who is the affected end user?

      Driver devs implementing the changes required by DRIVERS-1983.

      How does this affect the end user?

      The initial DNS seedlist discovery spec tests fail.

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

      The test failures will always happen after doing the driver changes required by DRIVERS-1983.

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

      Driver devs will have to investigate unexplained test failures.

      Is this issue urgent?

      No.

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      Yes.

      Attachments

        Issue Links

          Activity

            People

              matt.dale@mongodb.com Matt Dale
              matt.dale@mongodb.com Matt Dale
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: