[SERVER-41281] Modify ShardingTest so it can set startup parameters on each node individually Created: 22/May/19 Updated: 05/Dec/22 Resolved: 25/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-common-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
One would expect the above ShardingTest to create a cluster with two shards, each a replica set. Each mongod should have a different value for internalQueryExecYieldIterations 123, 456, 789 However, when you actually run this, none of the shards start up with the internalQueryExecYieldIterations parameter set at all. This is a problem for any server parameters. |
| Comments |
| Comment by Tommaso Tocci [ 25/Nov/22 ] |
|
it seems that In the last 3 years we didn't encounter this limitation. So we are closing this for now. |
| Comment by Ian Boros [ 28/May/19 ] |
|
This is no longer a 4.2 RC blocker because of the work-around described above! Since it sounded like the original fix for this broke numerous other tests, we're descheduling this, and I'm moving it to the sharding backlog.
Ted, can you post whatever recent progress you've made on the code review for if/when this gets picked up again? EDIT: Looks like I raced with Dave. |
| Comment by David Storch [ 28/May/19 ] |
|
ted.tuckman, due to the workaround which Ian has implemented, I'm going to remove this from the epic and flag it for re-triage. We can stop any further work on this task for now. |
| Comment by Ian Boros [ 27/May/19 ] |
|
I may have found a way around this problem (restarting nodes in the set with different values for setParameter) in which case we don't need to mark this as a release blocker anymore. Patch build is running. |