[SERVER-42112] uassert on _flushDatabaseCacheUpdates cmdResponse if not NamespaceNotFound in configsvrDropDatabase and configsvrCreateDatabase Created: 08/Jul/19 Updated: 29/Oct/23 Resolved: 17/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-10-21 |
| Participants: |
| Description |
|
We will now send _flushDatabaseCacheUpdates at the end of configsvrCreateDatabase to the primary shard, and at the end of configsvrDropDatabase to all shards. We should uassert on the command response, ignoring NamespaceNotFound, since v4.2 shards will return NamespaceNotFound (see |
| Comments |
| Comment by Githook User [ 17/Oct/19 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |