[SERVER-46546] Only seed the RNG once in sharding_multiversion tests Created: 02/Mar/20 Updated: 29/Oct/23 Resolved: 03/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.3 Desired |
| Fix Version/s: | 4.3.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2020-03-09 |
| Participants: |
| Description |
|
Currently, in the sharding_multiversion suite, we are seeding the random number generator for each replica set rather than seeding it only once. This makes reproducing the tests in sharding_multiversion more difficult.
Additionally, the check in shardingtest.js here should be checking jsTest.options().useRandomBinVersionsWithinReplicaSet instead of the no longer used jsTest.options().randomBinVersions. |
| Comments |
| Comment by William Schultz (Inactive) [ 04/Mar/20 ] | |||||
|
jason.chan I feel that this may be a more general issue whenever a test starts up multiple ReplSetTest instances. I recently encountered this in the disallow_adding_initialized_node1.js test e.g.
Ideally, it seems that we should only need to set a random seed once, globally, for each mongo shell process that we start up. I wonder if here we could set a seed only if it hasn't already been set previously. | |||||
| Comment by Githook User [ 03/Mar/20 ] | |||||
|
Author: {'username': 'jasonjhchan', 'name': 'Jason Chan', 'email': 'jason.chan@10gen.com'}Message: |