[SERVER-35369] The listCollections sent for aggregates should be robust to failure in continuous config stepdown suites Created: 01/Jun/18 Updated: 06/Dec/22 Resolved: 28/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 4.0.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In the continuous config stepdown test suites, it is possible for the listCollections sent as part of aggregate to fail if the config server just stepped down. Aggregate tests which target the config server (for the "admin" or "config" databases) running in such a suite should either be blacklisted or made more robust to these kinds of failures by switching the listCollections call from the legacy networking layer (which does not retry on network errors) to the helpers which provide retries on top of the ASIO networking layer. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 28/Jun/18 ] |
|
Won't Fix as per Nick's comment above. |
| Comment by Nicholas Zolnierz [ 08/Jun/18 ] |
|
Linking as related to |
| Comment by Esha Maharishi (Inactive) [ 01/Jun/18 ] |
|
max.hirschhorn the work in |
| Comment by Max Hirschhorn [ 01/Jun/18 ] |
|
esha.maharishi, would the work in this ticket also satisfy |
| Comment by Esha Maharishi (Inactive) [ 01/Jun/18 ] |
|
Note that blake.oler has a patch in code review to add a helper to Shard that can run listCollections under |