-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Server Tooling & Methods
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".
- is duplicated by
-
SERVER-75455 Improve asCluster with X509 command execution in ReplSetTest and ShardingTest
- Closed
- is related to
-
SERVER-55273 ReplSetTest and ShardingTest objects does not support x509 authentication
- Closed
- related to
-
SERVER-28376 ReplSetTest.initiate() should call awaitReplication before requesting node 0 to step up as primary
- Closed
-
SERVER-53812 replsettest.awaitReplication does not work with keyfile authentication
- Closed
-
SERVER-25976 Wait for replication of config.version write and config server index builds during ShardingTest setup
- Closed
-
SERVER-13112 Cannot use more than one ShardingTest helper with replica set shards
- Closed