[SERVER-46300] Set high election timeout in map_reduce_multiversion_cluster.js Created: 21/Feb/20 Updated: 12/May/20 Resolved: 01/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ali Mir | Assignee: | Ali Mir |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2020-02-24, Repl 2020-03-09, Repl 2020-03-23, Repl 2020-04-06 | ||||||||
| Participants: | |||||||||
| Description |
|
The jstests/multiVersion/map_reduce_multiversion_cluster.js test uses a sharded cluster with two, 2-node replica set shards. In order to prevent unwanted elections while testing the mapReduce command, we should set a high election timeout. |
| Comments |
| Comment by Ali Mir [ 01/Apr/20 ] |
|
This bug is related to a more general issue where commands are sent to recently-upgraded clusters before they have stabilized. The solution is addressed as a part of SERVER-47231. |