[SERVER-39659] router should uassert that there was no writeConcern error when processing _configsvrCreateDatabase response Created: 19/Feb/19 Updated: 29/Oct/23 Resolved: 07/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.10, 4.0.6, 4.1.8 |
| Fix Version/s: | 4.2.0-rc5, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | James Heppenstall (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-interns-2019, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Sharding 2019-06-17 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 6 | ||||||||
| Description |
|
Currently it only uasserts on the commandStatus and then tries to refresh its cache to find the new (supposedly durable) entry for the database, which can lead to commands failing with with "Database <> not found":
|
| Comments |
| Comment by Githook User [ 03/Jul/19 ] |
|
Author: {'name': 'Jamie Heppenstall', 'username': 'JamesHeppenstall', 'email': 'jamie.heppenstall@mongodb.com'}Message: (cherry picked from commit 0863aca0c6ad060ad241b7fa75fb03db06beccb0) |
| Comment by Githook User [ 07/Jun/19 ] |
|
Author: {'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com'}Message: |