[SERVER-70725] Cluster aggregate may incorrectly result in CollectionUUIDMismatch if fetching routing info fails Created: 20/Oct/22 Updated: 29/Oct/23 Resolved: 26/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.1, 6.0.3, 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| 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 | ||||||||||||||||||||
| Backport Requested: |
v6.1, v6.0
|
||||||||||||||||||||
| Sprint: | Execution Team 2022-10-31 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
If cluster aggregate's call to sharded_agg_helpers::getExecutionNsRoutingInfo fails, currently we throw CollectionUUIDMismatch if an expected collection UUID was provided. However, if the error is not specifically NamespaceNotFound then it's possible the database actually does exist and we should not throw CollectionUUIDMismatch. |
| Comments |
| Comment by Githook User [ 04/Nov/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 85a50585a0b5ea5b174dbb0c8678a85d68ac5d4e) |
| Comment by Githook User [ 04/Nov/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 85a50585a0b5ea5b174dbb0c8678a85d68ac5d4e) |
| Comment by Githook User [ 26/Oct/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |