[SERVER-53033] Investigate usages on "not master" error messages in sharding unittests Created: 23/Nov/20 Updated: 29/Oct/23 Resolved: 02/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2021-07-12 |
| Participants: |
| Description |
|
The following tests seems to attach "not master" error messages to error codes like NotWritablePrimary when constructing errors. We should investigate whether these strings are necessary, otherwise we should change them to "not primary" to be more in line with the new error messages we'll return with the hello command: |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 02/Jul/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}Message: |