[SERVER-55755] Add a 'does_not_support_stepdowns' tag to the geo_borders.js test Created: 02/Apr/21 Updated: 29/Oct/23 Resolved: 20/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2021-05-03 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 50 | ||||||||||||
| Description |
|
geo_borders.js first calls createIndex expecting it to fail, then secondly calls createIndex with a different spec expecting it to succeed. However, both requests have the same default index name, and due to the test suite stepping down the primary frequently, the second request can target a node that hasn't yet aborted the first request. Simple solution is to add the does_not_support_stepdowns tag to the test. This also protects the subsequent queries expecting to use the index against targeting a primary node with a still incomplete index. |
| Comments |
| Comment by Githook User [ 20/Apr/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |