Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
-
ALL
-
Security 2021-04-05
Description
When adding setParameters for sharding tests like this:
options = {
|
...,
|
other: {
|
mongosOptions: {
|
setParameter: {
|
param1: val,
|
param2 ...
|
}
|
},
|
}
|
}
|
st = new ShardingTest(options);
|
The test runner adds an extra setParameter - migrationLockAcquisitionMaxWaitMS for the mongos which causes it to fail to start. Instead, a user has to add set parameters like this - setParameter: "param1=val", which does not allow a user to specify multiple setParameters in an intuitive way (or possibly at all). See this example for how the ShardingTest set parameter needs to be specified.
Attachments
Issue Links
- is depended on by
-
SERVER-52944 Add additional audit sharding tests
-
- Closed
-