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

Refactor ShardingTest and ReplSetTest objects to use separate control and test connections

    XMLWordPrintable

Details

    Description

      Today, the ShardingTest and ReplSetTest objects used for writing integration tests in javascript depend on the same connections to underlying server nodes to do both control operations (stop the balancer before running this test, wait for replication to catch up) and test operations (test behavior of updating documents when the user has these permissions). This is particularly problematic for tests involving authorization, because the control operations should be done with the authority of the super user, while the test operations generally should operate with different privilege.

      An appropriate solution would be to change the implementation of ShardingTest and ReplSetTest to keep separate control and test channels, and to use the control channels internally for behaviors such as "awaitReplication" and "stopBalancer".

      Attachments

        Issue Links

          Activity

            People

              backlog-server-stm Backlog - Server Tooling and Methods (STM) (Inactive)
              schwerin@mongodb.com Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: